Skip to main content
Talk to an expert
AirFI Onboard WiFi

AirFi POS Integration Specialists

In-flight inventory and crew accounts always stay aligned iWeb syncs crew account balances, pricing and promotions to AirFi in real time, and exports in-flight sales and inventory movements back to ERP automatically so cabin and ground stay current. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

AirFiiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Magento Open Source · Adobe Commerce · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
00 · At a glance

AirFi at a glance.

Category
POS · retail · branch systems
Role in the estate
The trade counter, till and branch system - owns walk-in transactions, click-and-collect touch points and often the local customer relationship.
Commonly connects with
Commerce platforms · ERP · finance · OMS · order management · Payments
Typical use cases
Sync crew account balances and permissions between ground commerce and in-flight ordering · Move in-flight sales transactions and inventory movements back to ERP for reconciliation · Publish pricing and product availability to crew tablets in real time · Handle returns and adjustments from cabin sales back to the commercial ledger
Relevant services
BuildSupportPIM and DataRescue
01 · What you get

What an AirFi integration gives you.

In-flight inventory stays aligned

Cabin stock movements and sales automatically feed to ERP and warehouse systems. Physical and ledger stock remain in step without manual count reconciliation or missing transactions.

Crew accounts are current and trusted

Account balances, credit limits and permissions update automatically from ground systems into AirFi. Crew members and finance teams see a single source of truth for account state and purchasing rules.

Pricing is fresh and consistent

Price and promotion changes published in commerce flow to crew tablets in real time. Crew members and airline finance see the same pricing, eliminating ringing errors and margin leakage.

Sales transactions post automatically

In-flight sales and adjustments move directly to ERP for ledger posting and reconciliation. Month-end close is faster and audit trails are complete without manual data entry.

Offline cabin operations don't lose data

Sales captured during offline periods are reliably queued and posted when connectivity returns. No transactions are silently dropped and crew can operate confidently knowing sales will reconcile.

02 · When it's worth it

Where an AirFi integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Sync crew account balances and permissions between ground commerce and in-flight ordering
Move in-flight sales transactions and inventory movements back to ERP for reconciliation
Publish pricing and product availability to crew tablets in real time
Handle returns and adjustments from cabin sales back to the commercial ledger
Link in-flight customer profiles to ground loyalty and customer accounts
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

No native ground commerce integration

AirFi does not talk directly to ecommerce platforms or ERPs by default. Pricing, crew accounts, inventory and transaction data must be manually loaded or synced via custom integration.

Limited stock and inventory governance

AirFi tracks cabin inventory but has no native two-way sync with ERP or warehouse systems. Stock movements must be manually reconciled or exported and re-entered, creating audit and reconciliation risk.

No real-time customer account sync

Crew account balances, permissions and linked customer profiles do not automatically update from ground systems. Manual uploads or batch feeds are required, risking stale data during peak sales.

Limited pricing synchronisation

Price and promotion changes in ground systems do not automatically push to crew tablets. Pricing must be manually updated in AirFi, increasing the risk of stale or incorrect prices at checkout.

No automated transaction posting to finance

In-flight sales must be exported and manually imported into ERP or accounting systems. Transaction detail, timings and payment methods are not automatically reconciled, creating month-end delays and audit friction.

03b · Honest limits

When AirFi may not be the simplest fit.

A short, honest list. Not a warning; just where a different shape of system usually costs less to run.

A pure online business with no physical branches
No appetite to change branch staff workflow
A till system with no serious integration surface
Expecting the EPOS to solve omnichannel on its own
04 · The real work

The challenge in airline retail is keeping crew accounts, inventory and pricing in step across ground systems and in-flight tablets without creating offline brittleness or reconciliation delays.

05 · How it connects

How this integration connects to your estate.

AirFi holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Storefront independent. AirFi feeds stock, pricing, orders and customer data into your chosen platform.

System of record
Source / owner
AirFi
In-flight point of sale and crew mobile ordering interface
  • In-flight transaction capture (sales, refunds, adjustments)
  • Crew tablet ordering and checkout experience
  • Cabin-local product and pricing display
  • Offline transaction queuing during connectivity loss
  • Crew authentication and session state
iWeb integration layer
Customer-facing commerce
Commerce platform
Magento Open SourceAdobe CommerceShopify PlusBigCommerceOther storefronts
  • Product catalogue, base pricing and promotion authoring
  • Ground customer accounts and loyalty programme
  • Ecommerce storefront and online ordering
  • Customer-facing order status and tracking
  • Channel-specific pricing rules and availability
Connected neighbours
Integration layer
ERP or accounting system
Holds the ledger of record for crew accounts, general ledger, inventory and customer accounts; receives in-flight sales and adjustments via integration
Integration layer
PIM or commerce product system
Authors product names, descriptions, images, pricing and promotions; the integration pushes current prices and availability to crew tablets
Integration layer
Inventory or warehouse management
Holds cabin and central stock records; the integration exports in-flight sales and restocking movements to keep stock aligned
Integration layer
Crew or HR system
Source of crew identities, roles and permissions; may feed authentication and account rules to AirFi
Integration layer
Payment and banking systems
Process crew account debits, card payments and bank reconciliation; finance matches cabin transactions against deposits
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Magento Open Source
  • Adobe Commerce
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • SAP, Oracle NetSuite, Microsoft Dynamics 365 (ERP)
  • Infor, Epicor (ERP for aviation)
  • Shopify, BigCommerce (commerce platforms)
  • Inventory and warehouse management systems
  • Customer loyalty and account platforms
  • Identity and SSO (crew authentication)
  • Pricing and promotions engines
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

Ask us about your stack
07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into ERP
←From OTHER SYSTEMS
↔BOTH WAYS
Crew accounts and balance feeds: Crew account data, purchasing limits and credit balances flow from ground commerce or ERP into AirFi to keep cabin ordering rules and account visibility current
This includes staff discounts, account holds and purchasing restrictions.
Pricing and product catalogue: Product availability, pricing, product names and cabin-specific restrictions move from commerce or PIM into AirFi so crew members see the correct range and prices at checkout
Region or aircraft-type constraints are respected.
In-flight sales transactions: Completed cabin sales, refunds and adjustments flow to ERP as sales ledger entries and inventory movements
Transaction detail, timestamps, crew identifiers and payment method are captured for finance reconciliation and audit.
Cabin inventory movements: Stock movements from in-flight restocking, returns and adjustments feed back to ERP and warehouse management so physical and ledger stock stay in step
Cabin location and stock-take results are recorded.
In-flight promotions and discounts: Promotion rules, crew discounts and limited-time offers flow into AirFi from commerce systems, and redemption and usage data flow back to ground systems for campaign tracking and margin analysis.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Design the crew account and permission model

    iWeb defines how crew identifiers, account balances, purchasing limits and staff discounts map between ground commerce, ERP and AirFi. Ownership and refresh frequency are agreed upfront so data stays current.

  2. 02
    Build real-time pricing synchronisation

    iWeb constructs the pipelines so that price, promotion, availability and cabin-specific restrictions flow from commerce or PIM to AirFi as changes happen. Crew tablets stay current without manual updates.

  3. 03
    Automate in-flight transaction posting

    iWeb builds the export and ledger-posting flows so that completed sales, refunds and adjustments move from AirFi to ERP automatically. Transaction detail, GL codes and audit trails are preserved.

  4. 04
    Handle offline queuing and reconciliation

    iWeb designs the offline-queue architecture so that in-flight sales captured without connectivity are reliably held and posted when the aircraft reconnects. Exception queues and monitoring are built in.

  5. 05
    Monitor and alert on data drift

    iWeb establishes the observability so that pricing mismatches, missing transactions, stale accounts and connectivity issues are surfaced early. Operational teams know when the integration needs attention.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataCrew account balances and purchasing limits
Source / ownerGround ERP or commerce system
Maintained byFinance or crew HR team
NotesAirFi receives a read-only copy; account state changes are driven from the ground system and pushed to AirFi via integration.
DataIn-flight pricing and promotion rules
Source / ownerCommerce or PIM system
Maintained byMerchandising or product team
NotesAirFi is a display and ordering interface; price changes are authored in the ground system and synced to crew tablets before flights depart.
DataIn-flight sales transactions and order detail
Source / ownerAirFi at time of sale, then ERP for ledger
Maintained byAirFi during flight, ERP after posting
NotesAirFi captures the transaction; the integration extracts and posts it to ERP for financial recording and reconciliation.
DataCabin inventory movements and stock counts
Source / ownerERP or WMS
Maintained byWarehouse or inventory team
NotesAirFi records cabin stock usage; the integration exports movements back to ERP / WMS so physical and ledger stock stay aligned.
DataCrew profile and authentication
Source / ownerAirFi (sometimes linked to HR or SSO)
Maintained byAirFi administrator or HR system
NotesCrew login and permissions may be synced from SSO or HR systems; AirFi holds the cabin-facing identity state.
DataReturns, adjustments and discounts applied
Source / ownerAirFi at time of transaction
Maintained byAirFi, then ERP for adjustment posting
NotesReturns and manual discounts are recorded in AirFi; the integration captures detail and posts to ERP as adjustments or credit memos.
10 · Experienced integrator

Built airline retail integrations

iWeb has built in-flight ordering and payment integration across airline platforms. We understand how AirFi sits between crew workflows, cabin inventory and ground ERP / commerce systems and how to keep transaction data, account state and pricing aligned across both.

Designed crew account and permission models that sync from ERP and HR systems into AirFi without stale data or offline brittleness.
Built automated posting flows so that in-flight sales, refunds and inventory movements export to ERP and reconcile with bank deposits.
Handled offline queuing and reconnection logic so that transactions are reliably captured and posted even during long-haul flights or connectivity gaps.
Configured real-time pricing and promotion synchronisation so that crews see current prices and ground merchandise rules apply in the cabin.
Established observability and alerting so that operational teams know when account syncs, pricing or transaction posting need attention.

Enterprise digital commerce specialists since 1995

UK-based, employee-owned team

Adobe Gold Commerce Partner

ERP, PIM and operational integration experience

Build, replatform, rescue and long-term support

Platform-led where appropriate, integration-led across the wider estate

11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify crew account balances sync from ERP to AirFi and reflect in ordering limits without stale data.
Confirm in-flight sales are captured with full transaction detail and posted to ERP within the expected reconciliation window.
Test offline transaction queuing so that sales captured without connectivity are reliably held and posted when aircraft reconnects.
Validate pricing and promotion changes flow to crew tablets and crew see the correct price at checkout.
Confirm inventory movements from in-flight sales feed back to ERP and WMS so physical and ledger stock stay aligned.
Test refunds and adjustments so that crew can process them in flight and they post to ERP as adjustment entries with audit trail.
Verify exception alerts notify operational teams if account syncs fail, pricing is stale or transaction queues are building.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Crew accounts go stale between syncs

If account balances and permissions are synced infrequently or fail to push from ground systems, crew may be over-charged or denied legitimate purchases mid-flight. Offline crew tablets will apply old limits.

Pricing mismatches between ground and cabin

If pricing is not synced automatically or is synced out of step with ground promotions, crew will see different prices than ground customers. This creates confusion and margin loss.

In-flight sales are lost or delayed

If AirFi queuing fails during offline periods or if transactions are not reliably posted when connectivity returns, sales data is lost, inventory counts become wrong and month-end reconciliation fails.

Inventory movements don't feed back to ERP

If cabin stock movements and sales are not automatically exported to ERP, warehouse and finance teams see a different stock position than what is actually in the cabin. Ordering and reconciliation become unreliable.

Manual data entry becomes a hidden dependency

If pricing, accounts or transactions are not automated, operations staff fall back to manual uploads, spreadsheets or batch files. These become unmaintained and are forgotten during staff turnover, breaking the integration.

Payment method or tender confusion

If in-flight transactions do not capture payment method detail or if crew account debits are not reconciled against bank deposits, finance cannot match cabin sales to bank feeds or customer account ledgers.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about AirFi integrations.

How do we sync crew account balances from ERP to AirFi so cabin ordering stays aligned?

iWeb designs a scheduled or event-driven sync so that account balances, credit limits and permissions flow from ERP to AirFi. The frequency and trigger rules are agreed based on your operational rhythm and offline cabin requirements.

What happens if a crew member's account balance changes while the aircraft is offline?

If the aircraft is offline, crew tablets work with the last-synced account state. The integration queues any transactions that occur and posts them when connectivity returns. Balance updates are pulled at the next scheduled sync or at aircraft reconnection.

How do in-flight sales get posted to ERP and reconcile with bank deposits?

iWeb exports transaction detail from AirFi, maps it to ERP GL codes and posts it as sales ledger entries and inventory movements. Payment method and crew identifiers are preserved so that finance can reconcile cabin sales to bank feeds and crew account debits.

How do we handle pricing changes during the week if crews are flying?

iWeb builds the sync so that price and promotion changes published in your commerce system flow to AirFi and crew tablets in real time or at a scheduled interval before flights depart. Crews always see the current price without manual updates.

What if a price changes after an aircraft has launched and crew see the old price?

The integration timestamps price changes and tracks which version crews saw. Post-flight reconciliation compares the price crew charged against the current and historical price lists so that any pricing errors are caught and adjusted.

How do cabin inventory movements get reflected in the warehouse and ERP stock counts?

iWeb exports cabin stock movements (sales, returns, adjustments, restocks) from AirFi and posts them to ERP / WMS as inventory transactions. Physical and ledger stock stay aligned without manual count reconciliation.

What if crew process a refund or adjustment in flight?

Refunds and adjustments are captured in AirFi with timestamp, crew identifier and reason. The integration exports them to ERP as adjustment or credit memo entries so that ledger and inventory stay in step.

How do we link in-flight customers to ground loyalty or customer accounts?

iWeb maps crew identifiers (badge, name, flight number) to customer records in ERP or commerce. In-flight sales are posted against the crew's account so that loyalty points, account history and purchasing rules carry across both channels.

What observability do we have that the integration is working?

iWeb establishes monitoring so that you see real-time status of account syncs, pricing pushes, transaction exports and exception queues. Alerts notify you if a sync fails, if pricing is stale or if transactions are held in queue.

How do we rollback pricing or account changes if something goes wrong?

iWeb designs the sync so that you can recall the last good state of accounts or pricing from the ground system and push it back to AirFi. Transaction history is preserved so rollback does not erase sales data.

What happens if AirFi goes offline mid-flight?

AirFi is designed to queue transactions locally. Once connectivity returns, the integration automatically posts queued sales, adjustments and inventory movements to ERP. Monitoring alerts you if the queue is building or if posting fails.

How do we handle different pricing or promotions for different aircraft types or routes?

iWeb configures the pricing and product sync so that aircraft type, route, crew rank or seasonal rules can be applied when pushing to AirFi. Ground systems author the rules once and the integration applies them at deployment.

Can we test the integration without disrupting live flights?

Yes. iWeb sets up a parallel test environment so that you can validate account syncs, pricing, transaction posting and offline queuing without affecting crew-facing systems. Go-live is staged so that early flights are low-risk.

How long does it take to post in-flight transactions to ERP after a flight lands?

iWeb designs the posting interval based on your reconciliation window. Transactions are typically posted within minutes of aircraft reconnection so that finance can process and reconcile cabin sales the same day.

Next step

Have an AirFi integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →