Skip to main content
Talk to an expert
Orderwise ERP WMS ERP system

OrderWise integration for ecommerce fulfilment

Despatch and stock movement data stays synchronized across all channels. iWeb integrates OrderWise so orders flow into dispatch queues, tracking reaches customers, and stock movements close the loop with your ERP without manual workarounds. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

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

OrderWiseiWeb 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 OrderWise integration gives you.

Despatch accuracy and speed

Orders flow into OrderWise automatically, picking and packing begin sooner, and tracking reaches customers before they ask. No manual order entry, no transcription errors.

Stock reconciliation without drift

Warehouse stock movements (picks, adjustments, damage) flow back into ERP immediately so inventory records stay trusted and finance month-end reconciliation is clean.

Multi-channel fulfillment consistency

Each channel's dispatch rules (carrier, packaging, delivery service) are applied uniformly so a Shopify order follows the same workflow as a marketplace order without manual intervention.

Return and RMA visibility

Returns from customers trigger RMA workflows in OrderWise that flow back to commerce so refund status and restock dates are visible to both warehouse and ecommerce teams.

Reduced support escalations

Customers see real tracking numbers and live carrier status; warehouse staff know which orders are stuck and can action them before they become complaints.

02 · When it's worth it

Where a OrderWise integration earns its place.

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

Publish order and fulfilment instructions from commerce into OrderWise dispatch queues
Return despatch confirmations, tracking numbers and carrier data to storefronts and customers
Sync stock movements and warehouse transactions back into ERP inventory records
Apply carrier selection rules and fulfillment logic consistently across all channels
Surface and retry failed dispatch events before orders go out of sync
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.

Carrier API coverage gaps

OrderWise integrates common carriers, but niche or regional carriers may not have native label / tracking APIs. Manual label feeds or custom carrier modules become necessary, slowing adoption.

Return workflow inflexibility

OrderWise RMA capture is linear; complex return scenarios (partial restocks, inspections, credit holds) often require manual intervention or external OMS orchestration.

Stock buffer and reservation logic

OrderWise does not own inventory buffers or pre-dispatch reservations; those sit in commerce or ERP. Oversell and allocation conflicts require pre-integration governance setup.

Multi-warehouse dispatch rules

Distributed fulfillment across multiple warehouses with complex proximity or load-balancing rules requires custom rule configuration; there is no turnkey multi-site optimisation.

Real-time stock sync latency

OrderWise stock updates to ERP are typically batch or event-driven; during peak volumes or carrier outages, latency between dispatch and ERP visibility can drift.

04 · The real work

Despatch state and stock visibility often diverge when each system owns a piece of the truth; OrderWise as single source of fulfillment record removes reconciliation guesswork but demands reliable flows in and out.

05 · Where it sits

Where this integration sits in your estate.

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

Works across the whole stack. Connect OrderWise to your storefront, ERP and everything between.

System of record
Source / owner
OrderWise
System of record for dispatch instructions, tracking and fulfillment state
  • Dispatch task creation and prioritisation
  • Label generation and tracking number capture
  • Carrier rules and fulfillment logic
  • Return and RMA workflows
  • Warehouse stock movement records
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Order capture and initial fulfillment intent
  • Customer delivery address and contact
  • Order cancellation signals
  • Tracking visibility to customers
  • Channel-specific fulfillment preferences
Connected neighbours
Integration layer
ERP
Receives stock movements and adjustments; provides base inventory for allocation. Finance system of record for cost and reconciliation.
Integration layer
Carrier APIs
Provide label generation, tracking updates and delivery confirmation. OrderWise is the integration hub for multi-carrier management.
Integration layer
Commerce platform(s)
Source of confirmed orders; displays tracking and delivery status to customers. Receives despatch confirmations and cancellation acknowledgements.
Integration layer
Order management system (OMS)
May sit between commerce and OrderWise to orchestrate multi-channel orders and returns logic before dispatch instructions are created.
Integration layer
Marketplace connectors
Each marketplace sends its orders into OrderWise with channel-specific rules; despatch and tracking flow back to each marketplace.
Integration layer
Returns and customer service platform
Issues RMA requests that flow into OrderWise; receives inbound stock and refund status updates.
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)
  • ERP (NetSuite, Sage 200, SAP, Infor)
  • Order management system (OMS)
  • Carrier APIs (DPD, Hermes, Royal Mail, FedEx, UPS)
  • Inventory and stock control systems
  • Accounting and finance ledgers
  • Marketplace connectors (Amazon, eBay, Shopee)
  • Customer service and returns platforms
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 COMMERCE & ERP
←From COMMERCE
↔BOTH WAYS
Order capture and fulfillment instructions: Confirmed orders flow from your ecommerce platform into OrderWise with line items, delivery address and special handling flags
OrderWise creates dispatch tasks and picks against warehouse stock.
Despatch confirmations and tracking: Once OrderWise completes picking and packing, it sends back despatch confirmation, tracking numbers, label images and carrier details so customers receive real-time shipment visibility.
Stock movements and warehouse adjustments: Stock picks, adjustments, damage and write-offs recorded in OrderWise flow back into your ERP inventory ledger so finance and stock control remain reconciled.
Return and RMA handling: Return authorisations from commerce or customer service trigger reverse flows into OrderWise; inbound stock is captured and flows back to ERP as available inventory.
Channel-specific dispatch rules: Carrier preferences, packaging rules and delivery service levels from each sales channel are applied during dispatch so marketplace orders follow their specific fulfillment logic.
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 end-to-end fulfillment flows

    We map how orders flow from each commerce channel into OrderWise, how despatch confirmations and tracking get back to customers, and how stock adjustments close the loop with ERP.

  2. 02
    Build carrier and label integrations

    We connect OrderWise to your chosen carriers so labels print and tracking updates flow back to commerce storefronts automatically; we handle fallback printing and manual label workflows for carriers without APIs.

  3. 03
    Govern dispatch and fulfillment logic

    We document which team owns carrier rules, packaging rules, returns workflows and stock write-off policies so OrderWise configuration changes do not silently break a channel or create reconciliation gaps.

  4. 04
    Monitor and retry failed shipments

    We build observability so despatch failures, missing tracking events and stock movement gaps are visible; we implement retry queues so temporary carrier outages do not strand orders.

  5. 05
    Support multi-channel RMA workflows

    We design how returns from different channels (marketplace, owned ecommerce, customer service) all feed into OrderWise so inbound stock reconciles correctly and refund status flows back to the originating channel.

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
DataDispatch instructions and fulfillment queues
Source / ownerOrderWise
Maintained byWarehouse operations and fulfillment team
NotesCommerce captures the order; OrderWise holds the fulfillment state and dispatch task queue.
DataDespatch confirmations, labels and tracking numbers
Source / ownerOrderWise
Maintained byOrderWise and carrier systems
NotesOrderWise creates the shipment record; carriers provide tracking; commerce displays tracking to customers.
DataStock movements, picks and warehouse adjustments
Source / ownerERP
Maintained byWarehouse team records in OrderWise; ERP receives and reconciles
NotesOrderWise captures the physical movement; ERP inventory ledger is system of record for balance and cost.
DataCarrier selection rules and fulfillment logic
Source / ownerOrderWise
Maintained byFulfillment and operations team
NotesRules are configured in OrderWise; channel-specific overrides must be documented so inadvertent global changes do not occur.
DataReturns, RMAs and inbound stock
Source / ownerOrderWise
Maintained byWarehouse and returns team
NotesRMA requests flow from commerce into OrderWise; inbound stock is recorded there and flows back to ERP as available.
DataIntegration transport and exception handling
Source / ownerIntegration platform or middleware
Maintained byiWeb and operations team
NotesFailed messages, retries and reconciliation gaps are monitored; escalation paths are owned by the integration team.
10 · Experienced integrator

Built this before

iWeb has designed and deployed OrderWise integrations across ecommerce estates ranging from single-channel to multi-marketplace environments. We understand how OrderWise sits between commerce, ERP and the warehouse, and how to route despatch confirmations, tracking and stock movements reliably.

We design carrier routing and fallback logic so labels print even when a preferred carrier is unavailable, and tracking reaches customers on time.
We integrate OrderWise stock movements into ERP so inventory reconciliation is automatic and month-end does not require manual stock counts or spreadsheet fixes.
We handle returns workflows across multiple channels so inbound stock is tracked, inspected and restocked uniformly regardless of where the customer initiated the return.
We monitor dispatch queues and exception patterns so your team can surface and action stuck orders before they breach fulfillment SLAs or trigger escalations.
11 · Before launch

What we test before launch.

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

Verify order volume and line item accuracy flows from all channels into OrderWise within SLA without data loss or truncation.
Confirm tracking numbers are published back to commerce within 30 minutes of carrier confirmation and display to customers correctly.
Test stock pick recording, damage adjustments and write-offs flow to ERP on schedule and reconcile in the next inventory cycle.
Validate carrier failover and manual label fallback paths work when a carrier API is unavailable or times out.
Confirm order cancellations from commerce stop picking in OrderWise and alert warehouse staff if stock has already been pulled.
Verify returns from each channel create RMA records in OrderWise and inbound stock flows back to ERP as available within 48 hours.
Check exception queue visibility for stuck orders, failed label prints and missing tracking so your team can action them before SLA breach.
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 held in unmonitored dispatch queues

Orders flow into OrderWise but do not move to picking because a carrier API is down, a rule misfires or a warehouse team has not actioned the batch. No alert surfaces until customers complain.

Tracking numbers not reaching customers

OrderWise generates tracking but the flow back to commerce is broken, slow or incomplete. Customers see orders marked shipped with no tracking link, generating support tickets and refund requests.

Stock movements not reflected in ERP

Warehouse picks, damage, adjustments are recorded in OrderWise but the feed to ERP is delayed or silent. Finance sees inflated inventory; stock control teams cannot trust the records.

Channel-specific rules silently overridden

A carrier preference or packaging rule configured for one channel (e.g. Shopify) is applied globally by accident. Orders ship incorrectly; marketplace ratings drop before the error is caught.

Return flows lost between channels and warehouse

A customer initiates a return on Shopify; the RMA does not reach OrderWise. Stock sits at the warehouse unlabelled. Finance books a credit but inventory is never restocked.

Despatch failures during peak or carrier outages

A carrier API becomes intermittently unavailable during a promotional surge. Some orders get labels, others hang. No retry queue exists; manual intervention is the only path forward.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about OrderWise integrations.

How do orders flow from our ecommerce platform into OrderWise?

Confirmed orders are published from your commerce platform (or OMS if you have one) to OrderWise via API or file feed with line items, delivery address, special instructions and any channel-specific fulfillment rules. OrderWise creates a dispatch task and assigns picking work.

When do customers see tracking numbers?

Once OrderWise sends a dispatch confirmation to the carrier and receives a tracking number back, that number flows immediately back to your commerce platform so the customer sees it in their order status within minutes of shipment.

How do warehouse stock adjustments get back to our ERP?

Stock picks, damage write-offs, and other warehouse adjustments recorded in OrderWise are published to your ERP via API or file so your inventory ledger stays in sync. Batch or event-driven feeds can be configured depending on your reconciliation cycle.

What happens if a carrier API goes down?

If a carrier is unavailable, OrderWise can queue the shipment for retry or route it to an alternative carrier if rules allow. The integration includes exception monitoring so your team is alerted; manual label printing is a fallback.

How do we handle returns and refunds?

Return requests from customers trigger RMA workflows in OrderWise. Once inbound stock is received and inspected, it flows back to ERP as available inventory and a credit is issued. Returns from different channels (marketplace, owned ecommerce) all feed the same OrderWise RMA process.

Can we apply different fulfillment rules to different sales channels?

Yes. Each channel can specify its own carrier preferences, packaging standards and service levels. These rules are embedded in the order when it enters OrderWise so a Shopify order follows Shopify fulfillment logic while a marketplace order follows its own rules.

How do we monitor if orders are stuck in dispatch?

The integration includes observability dashboards that track order age in each dispatch state. Alerts surface when orders exceed fulfillment SLAs so your team can investigate and manually action them before they breach promised delivery dates.

What happens if an order is cancelled after it enters OrderWise?

Commerce sends a cancellation signal to OrderWise. If the order has not yet been picked, OrderWise removes it from the dispatch queue. If it has been picked, your warehouse team is alerted so they can stop processing or return the picked stock.

How do we handle multi-warehouse fulfillment?

OrderWise can route orders to different warehouses based on stock availability or proximity rules. Each warehouse records its own picks and adjustments; all movements flow back to ERP so corporate inventory is always accurate.

Who owns the carrier integration if a carrier changes their API?

iWeb owns the technical integration layer and alerts your team to API changes. Your fulfillment team owns the business logic of which carriers to support and when to add new ones; we implement the technical connection.

Can we retry failed label printing or tracking lookups?

Yes. The integration includes a retry queue for temporary failures like carrier timeouts or temporary API unavailability. Your team can also trigger manual retries for specific orders from an exception console.

How do we reconcile dispatch data with our finance systems?

Despatch confirmations are immutable once published; they feed into invoicing and revenue recognition. Stock movements flow to ERP so cost of goods sold is accurate. The integration includes pre-launch reconciliation testing to ensure despatch and stock align.

Next step

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