Skip to main content
Talk to an expert
Lionwheel logo

Lionwheel integration for ecommerce fulfilment

Orders ship faster when warehouse executes with clarity iWeb connects your commerce platform and OMS to Lionwheel so orders flow in with complete context, despatch closes with tracking in step, and stock movements feed ERP inventory in real time. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: shipping connector, warehouse integration, fulfilment plugin, app.

LionwheeliWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Shopify Plus · BigCommerce · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a Lionwheel integration gives you.

Orders reach the warehouse reliably

Commerce orders, OMS instructions and marketplace orders flow into Lionwheel without loss or duplication. Each order carries the routing, carrier and handling rules needed for warehouse staff to execute correctly.

Despatch closes in near real time

Once a shipment leaves the warehouse, tracking and despatch data flow back to commerce and customer notifications immediately. Shoppers see status updates the same day, and commerce accounting recognises the sale as complete.

Stock and ERP stay in step

Pick events, pack confirmations and cycle-count adjustments flow back to ERP so stock availability reflects warehouse reality. Oversell risk drops and inventory reconciliation becomes a matter of data integrity, not manual guesswork.

Returns flow from warehouse to refund

Returned items scanned inbound in Lionwheel trigger RMA creation, refund signals and restocking in ERP and commerce. Customers get refunded on time and stock re-enters the correct location.

Exceptions surface and escalate

Unshipped orders, carrier rejections and label failures appear in a monitored exception queue with context about which channel, customer and warehouse location is affected. Teams respond within minutes, not after customer contact.

02 · When it's worth it

Where a Lionwheel integration earns its place.

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

Route orders from multiple commerce channels and marketplaces into Lionwheel for unified warehouse processing
Send despatch confirmations, tracking numbers and label data back to storefronts and customer notifications
Synchronise warehouse stock movements and cycle-count adjustments back to ERP and commerce stock records
Orchestrate returns and RMA workflows, sending refund signals and restocking instructions through the system
Monitor exception queues for unshipped orders, carrier failures and label-generation breakages
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.

Limited multi-channel order routing logic

Lionwheel may not natively rank, split or route orders by location, carrier preference or channel-specific delivery rules. iWeb defines routing policies before data enters the warehouse.

Weak exception visibility across channels

When orders fail to ship or labels break, visibility across multiple commerce channels and marketplaces is limited. iWeb builds centralized exception queues and alert routing.

Stock reconciliation drift with ERP

Warehouse cycle counts and pick confirmations may not automatically reconcile with ERP inventory. Manual reconciliation or export workflows often sit between the two systems.

Returns workflow gaps between warehouse and commerce

Return items may be received in Lionwheel but not automatically flow back to commerce or ERP as refundable stock. Restocking instructions often require manual entry.

Carrier and label provider outages not surfaced

When a label provider or carrier API is down, Lionwheel may queue orders without alerting teams to the underlying outage. Silent failures can delay despatch by hours.

04 · The real work

Silent despatch delays often hide behind the warehouse wall. Connecting Lionwheel's pick and pack events back to commerce and ERP visibility lifts them early.

05 · Where it sits

Where this integration sits in your estate.

Lionwheel 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.

Connect across your stack. Lionwheel plugs into the systems that run your trading operation, whichever ecommerce platform sits at the front.

System of record
Source / owner
Lionwheel
Warehouse execution and despatch operations layer
  • Pick and pack workflow execution
  • Despatch confirmation and label generation
  • Warehouse stock movement events
  • Returns inbound scanning and RMA initiation
  • Carrier and exception visibility at warehouse level
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Order placement and customer cart
  • Storefront and checkout experience
  • Customer account and order history
  • Initial order status and notification triggers
  • Refund and return initiation from customer perspective
Connected neighbours
Integration layer
Commerce platform or OMS
Routes orders to Lionwheel with allocation and carrier rules; receives despatch and tracking events to close orders.
Integration layer
ERP system
Holds stock ledger and customer accounts; receives pick and stock-movement events from Lionwheel; sends inventory availability to commerce.
Integration layer
Customer notifications and support
Receives despatch, tracking and RMA data from Lionwheel; sends to customer email and support systems; teams use tracking for inquiries.
Integration layer
Label and carrier providers
Receive shipment detail from Lionwheel; return labels and tracking numbers; may go down, affecting despatch workflow.
Integration layer
Reporting and analytics
Consumes despatch events, shipment detail and latency data from Lionwheel to build warehouse KPI dashboards.
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)
  • Adobe Commerce
  • Magento Open Source
  • Shopify Plus
  • BigCommerce
  • Other storefronts
Surrounding systems (examples)
  • SAP, NetSuite, Sage or in-house ERP
  • Brightpearl, Akeneo or other OMS
  • Shopify, custom headless or marketplace storefronts
  • Klaviyo or Iterable for customer notifications
  • Amazon or eBay marketplace connectors
  • Stripe or other payment processors
  • TaxJar or Avalara for tax and compliance
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.

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 LIONWHEEL & ERP
↔OUT OF LIONWHEEL & BOTH WAYS
Order and fulfilment instructions: Orders flow from commerce platforms, OMS and marketplaces into Lionwheel with line-item detail, shipping address, special handling flags and carrier preference
The warehouse uses this to allocate stock, pick lines and prepare despatch.
Despatch confirmations and tracking: Once lines are packed and labels printed, Lionwheel sends despatch events, tracking numbers and carrier details back to commerce, OMS and customer-notification systems so the shopper sees the shipment update and fulfilment closes.
Stock movements and cycle counts: Warehouse picks, pack-complete events and cycle-count adjustments flow to the ERP so inventory ledgers stay current and stock availability on the storefront matches what the warehouse holds.
Returns and RMA data: Inbound return items, RMA numbers and restocking instructions flow out to ERP and OMS so refunds can be processed, stock re-entered and customer accounts reconciled.
Carrier and label exceptions: Label-generation failures, carrier rejections and unshipped-order alerts flow into monitoring dashboards; corrected data and resend instructions flow back into Lionwheel to resume despatch.
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
    Order routing and orchestration

    iWeb defines rules for where orders are fulfilled from (location, channel, carrier preference), how they are split across locations, and how dropship or outsourced inventory is handled. Rules are applied before order data enters Lionwheel.

  2. 02
    Despatch and tracking closure

    iWeb ensures that the moment Lionwheel confirms a shipment, tracking numbers, carrier data and despatch status flow back to the storefront, OMS and customer-notification system. No manual export or delayed updates.

  3. 03
    Stock reconciliation and cycle counts

    iWeb maps pick, pack and cycle-count events from Lionwheel to ERP inventory updates, complete with location, cost centre and stock-type rules. Warehouse truth feeds ecommerce availability in near real time.

  4. 04
    Returns and RMA orchestration

    iWeb builds the inbound-return workflow: items scanned into Lionwheel trigger RMA numbers, refund signals and restocking events in ERP and commerce. Refunds and restock happen together, not weeks apart.

  5. 05
    Carrier and exception monitoring

    iWeb sets up observability so label-generation failures, carrier rejections, rate-lookup errors and unshipped-order queues are monitored and alerted. Fallback routing or manual escalation paths are pre-defined.

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
DataDespatch instructions and order detail
Source / ownerCommerce platform, OMS or order system (source)
Maintained byCommerce / OMS teams define what flows into Lionwheel; iWeb integration ensures completeness and routing rules are applied
NotesLionwheel receives and executes; does not own the order truth, which lives in commerce or OMS.
DataDespatch confirmations and tracking numbers
Source / ownerLionwheel (source)
Maintained byWarehouse operations confirm shipment; iWeb integration sends tracking data back to commerce, OMS and customer notifications
NotesLionwheel is authoritative for when a shipment left the warehouse; commerce and OMS consume the signal to close fulfilment.
DataStock movements and warehouse pick events
Source / ownerLionwheel (source of warehouse truth)
Maintained byWarehouse staff execute picks; iWeb integration translates pick and pack events into inventory adjustments for ERP
NotesERP inventory ledger is the business record; Lionwheel is the source of transaction detail that feeds it.
DataReturns and RMA workflows
Source / ownerLionwheel (inbound transaction source)
Maintained byWarehouse scans returned items; iWeb integration sends RMA and restocking data to ERP and commerce for refund and re-entry
NotesRefund and restock authority sits with ERP and commerce; Lionwheel initiates the event.
DataCarrier selection and label rules
Source / ownerCommerce or OMS (policy source)
Maintained byCommerce or OMS team owns carrier rules and special handling; iWeb integration ensures Lionwheel receives and applies them
NotesLionwheel executes labels against the rules it receives; does not own the rule logic.
DataException queues and unshipped-order tracking
Source / owneriWeb integration layer (monitors and routes)
Maintained byiWeb monitoring stack detects failures; operations and customer service own resolution
NotesExceptions are surfaced for human action; the underlying order truth stays in commerce or OMS.
10 · Experienced integrator

Built this before

iWeb has integrated Lionwheel with commerce platforms, OMS systems and ERP across multiple retail and ecommerce estates. We understand how warehouse execution sits between order routing and financial close, and where the hand-offs between systems break down.

Designed order-routing rules and carrier logic so Lionwheel receives orders that are ready to allocate and pick, not raw commerce orders.
Built despatch-closure workflows where tracking and carrier data flow back to commerce and customer notifications in near real time.
Mapped stock movements, pick events and cycle counts from Lionwheel into ERP inventory so warehouse truth feeds ecommerce availability continuously.
Orchestrated returns workflows from warehouse inbound through RMA generation, refund signals and restocking in ERP, closing the refund-to-restock loop.
Set up monitoring and exception queues for unshipped orders, carrier failures and label-generation errors so operations respond within minutes, not after escalation.
11 · Before launch

What we test before launch.

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

Verify that a sample order from each commerce channel and marketplace flows into Lionwheel with complete line detail, address and carrier rules intact.
Confirm that a picked and packed shipment generates a despatch event, tracking number and label link that reach the storefront and customer email within 5 minutes.
Test stock reconciliation: pick an item in Lionwheel and verify that ERP inventory and storefront availability update within 1 minute, not hours.
Send a test return inbound and confirm that Lionwheel generates an RMA, a refund signal reaches ERP and commerce, and stock is re-entered to the correct location.
Simulate a label-provider outage and verify that the exception is surfaced in a monitored dashboard within 2 minutes, not after a customer complaint.
Test order cancellation: cancel an order in commerce before Lionwheel ships it and confirm that the order is removed from the warehouse queue.
Validate that oversold or out-of-stock orders are held in an exception queue with clear reason codes, not silently failing to allocate.
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.

Orders stuck in Lionwheel without despatch

When orders arrive in Lionwheel but fail to allocate (oversell, out-of-stock, invalid address), they may sit in a queue no one is monitoring. Despatch delay goes unnoticed for hours until customer contacts support.

Tracking data lost between warehouse and storefront

Lionwheel confirms shipment and prints a label, but the tracking-number export fails or is delayed. Customers wait for tracking emails that never arrive, and customer service has no way to link the shipment back to the order.

Stock counts drift between warehouse and ERP

Lionwheel records a pick, but the message to ERP is delayed or fails silently. The storefront still shows the item as available, oversell happens, and the warehouse discovers the mismatch during cycle count.

Returned items not flowing to refund

Customer returns an item; it arrives at the warehouse and is scanned into Lionwheel. But the return signal does not reach ERP or commerce, so the refund is never triggered and stock is never re-entered.

Carrier outage silently blocking all despatch

Label-provider API or carrier integration goes down. Lionwheel queues orders without surfacing the underlying outage. No one alerts operations until dozens of orders are backlogged and customers start complaining.

Multi-channel orders losing context through warehouse

Orders from multiple channels (ecommerce, marketplace, B2B) all enter Lionwheel with different required fields or carrier rules. Without clear channel-specific handling logic, orders fail validation or are routed incorrectly.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Lionwheel integrations.

How do orders get into Lionwheel from multiple channels?

Commerce platforms, OMS and marketplaces all send order data to Lionwheel via the integration. iWeb defines the order-routing rules first—which location fulfils which channel, how orders are split, carrier preferences—so Lionwheel receives orders that are ready to allocate and pick.

What happens if Lionwheel is down?

iWeb sets up monitoring so a Lionwheel outage is detected immediately. Orders either queue safely in the source system (commerce or OMS) or are routed to a fallback warehouse, depending on your architecture. The important thing is that no orders are silently lost.

How does tracking get back to customers?

Once Lionwheel confirms shipment and prints a label, the tracking number and carrier data flow back to the storefront and customer-notification system in near real time. Customers receive tracking emails the same day, and your customer-service team can reference the shipment immediately.

How do you handle stock reconciliation between Lionwheel and ERP?

iWeb maps pick, pack and cycle-count events from Lionwheel into ERP inventory transactions. Stock adjustments flow continuously so ecommerce availability matches warehouse truth. Cycle counts and variance are flagged for investigation, not ignored.

What if an order oversells?

iWeb works with your OMS or routing logic to allocate orders to the warehouse that holds the stock. If stock is not available anywhere, the order can be held for restock, backordered with a customer commitment, or cancelled—depending on your policy. Lionwheel receives only orders that are safe to fulfil.

How are returns handled from Lionwheel back to refund?

When a customer returns an item, it is scanned inbound into Lionwheel. The inbound event triggers an RMA number, a refund signal in ERP or commerce, and a restocking transaction. Refunds and stock re-entry happen together, not weeks apart.

What if a label provider or carrier API fails?

iWeb sets up monitoring for label-generation failures and carrier-integration errors. When a carrier is down, the exception is surfaced immediately so operations can reroute via a backup carrier or hold despatch until the primary carrier is back. No silent failures.

How do you handle different carrier rules across channels?

iWeb works with your commerce or OMS system to define carrier rules and special handling per channel. When an order enters Lionwheel, it carries these rules so the warehouse staff apply the right carrier, service level and label format.

What if a customer changes an order while it is in the warehouse?

Order modifications are handled at the source (commerce or OMS) before shipment. If a change comes in after the order enters Lionwheel, it must flow back as a cancel and rebooking or as a special instruction. iWeb ensures that order modifications are visible to warehouse staff and do not cause mis-shipments.

How do you monitor unshipped orders?

iWeb builds an exception queue that tracks orders in Lionwheel that have not shipped within an expected timeframe. The queue shows why each order is held—oversell, address issue, missing address, carrier unavailable—so operations can prioritize resolution.

How does Lionwheel fit with your OMS?

Lionwheel is the warehouse-execution layer. An OMS (if you have one) handles order routing, allocation and split-shipment logic. iWeb ensures that the OMS sends fulfillment instructions to Lionwheel and that Lionwheel sends back despatch and tracking events so the OMS can close the order and notify the customer.

How do you handle multi-location fulfillment?

If orders are fulfilled from multiple warehouse locations, iWeb works with your OMS or routing logic to allocate each line to the right location. Each location's Lionwheel instance (or a central Lionwheel with location routing) receives its allocated orders and sends back despatch and stock-movement events. Cross-location transfers are handled via your transfer workflow.

What observability and monitoring does iWeb provide?

iWeb sets up dashboards and alerts for order inflow to Lionwheel, despatch throughput, unshipped-order queues, carrier and label failures, stock-movement accuracy and return-to-refund latency. You know in near real time if anything is stuck or degraded.

Can the integration handle dropship or outsourced inventory?

Yes. iWeb works with your OMS or routing logic to identify which orders go to Lionwheel (internal warehouse) and which go to a dropshipper or 3PL. Lionwheel receives only orders it should fulfil. Dropship orders are routed separately and tracked via a different despatch path.

Next step

Have a Lionwheel 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 →