Skip to main content
Talk to an expert
Cin7 Core logo

Cin7 Core integration for ecommerce fulfilment

Orders ship on time and stock never oversells. Cin7 Core integration routes orders to the right warehouse, syncs accurate stock back to commerce, and ensures tracking and returns flow back without delay. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

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

Cin7 CoreiWeb 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 Cin7 Core integration gives you.

Orders route to fulfillment automatically

Once integration is live, orders from commerce land in Cin7 with correct location assignment and priority. No manual dispatch queue triage or re-entry needed.

Stock availability matches warehouse reality

Shoppers see accurate available quantities because Cin7 stock syncs back to commerce after every receive, pick, and adjustment. Backorders are honest.

Customers get tracking faster

Despatch confirmations and carrier tracking flow back to commerce automatically so order status pages and shipping notifications update without delay.

Finance reconciliation is daily, not weekly

Stock movements in Cin7 create ERP journal entries on the same day, so month-end reconciliation is a verification step, not a week-long chase.

Returns do not disappear

Returned items flow into Cin7 receiving with clear RMA traceability, and refund instructions sync back to commerce and ERP on a managed schedule.

02 · When it's worth it

Where a Cin7 Core integration earns its place.

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

Route orders from commerce into warehouse dispatch queues with location rules
Synchronise available stock back to commerce as warehouse transactions occur
Ingest tracking and despatch confirmation events to update customer fulfillment status
Manage returns and RMA workflows between commerce, Cin7, and receiving
Track stock movements across pick locations and reconcile with ERP balances
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.

Location rules and routing logic are manual

Cin7 does not know your commerce channel priorities or drop-ship supplier thresholds. You must configure which orders route to which locations, and those rules drift if your warehouse footprint changes.

Carrier integration is limited

Cin7 connects to major carriers but not all regional or speciality shipping partners. Label generation and tracking sync may require custom middleware or manual carrier API calls.

Stock allocation and overbooking control are basic

Cin7 holds a single available quantity per location; it does not natively manage channel-specific reserve pools or handle real-time overbooking prevention across multiple sales channels simultaneously.

No built-in order acknowledgement or exception queue

Failed orders, unshippable items, or stock exceptions land in Cin7 but have no governed escalation path back to commerce or customer service. Manual review is required.

Warehouse labour and task sequencing are not exposed

Cin7 manages inventory and despatch but does not expose pick wave planning, labour scheduling, or task-sequence optimisation. Real-time warehouse activity is opaque to commerce.

04 · The real work

The gap between order promise and actual despatch often exposes weak communication between warehouse operations and commerce; integration removes that friction by making stock and dispatch state visible to both sides in real time.

05 · Where it sits

Where this integration sits in your estate.

Cin7 Core 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. Cin7 Core feeds stock, pricing, orders and customer data into your chosen platform.

System of record
Source / owner
Cin7 Core
System of record for warehouse inventory, despatch and returns fulfilment
  • Available stock position and location depth
  • Despatch instructions and picking queues
  • Tracking and label data
  • Returns receiving and RMA disposition
  • Stock movements and warehouse transactions
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceShopify PlusBigCommerceOther storefronts
  • Order capture and customer communication
  • Catalogue and inventory display
  • Refund and credit processing
  • Backorder customer notifications
Connected neighbours
Integration layer
ERP
Receives stock-movement journals from Cin7; holds nominal codes and VAT treatment; is system of record for GL and balance-sheet balances.
Integration layer
Carrier systems
Provide rate quotes and label generation; Cin7 publishes tracking back to commerce after carrier handoff.
Integration layer
Order management system
Sources orders into Cin7; receives despatch and tracking updates; triggers refund and credit workflows when RMAs close.
Integration layer
Customer service platform
Consumes order status, tracking, and RMA progress so agents can respond to customer enquiries without consulting multiple systems.
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)
  • Order management system (custom or COTS OMS)
  • Commerce platform
  • Carrier and shipping integration
  • Returns management system
  • Customer service platform
  • Analytics and BI warehouse
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 and fulfillment instructions: Orders placed in your storefront flow into Cin7 with line items, delivery addresses, and any location preferences
Cin7 queues them for pick and pack against warehouse stock.
Available stock and location depth: Cin7 publishes inventory position back to the ecommerce platform so shoppers see accurate availability and backorder status
Stock updates reflect completed receives and despatch events.
Dispatch and tracking events: When orders are shipped, Cin7 sends despatch confirmations, carrier tracking numbers, and label data back to commerce for customer notification and order status pages.
Stock movements and journal entries: Warehouse transactions in Cin7 (receives, picks, adjustments) feed into the ERP so finance and inventory balances stay aligned with physical warehouse state.
Returns and RMA events: Returned items flow into Cin7 for receiving and inspection; RMA dispositions and refund instructions flow back to commerce and ERP for credit processing.
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 and build location routing

    We map your warehouse locations, channel priorities, and drop-ship rules into Cin7 so orders route to the correct fulfillment queue automatically based on inventory depth and shipping origin.

  2. 02
    Establish two-way stock sync

    We configure Cin7 to publish available stock, location depth, and overbooking status back to your commerce platform on a cadence that prevents oversell while preserving fulfillment agility.

  3. 03
    Build exception and escalation handling

    We create a queue for unshippable items, stock exceptions, and carrier failures so they surface to the right team with clear context, not buried in Cin7 logs.

  4. 04
    Integrate returns and RMA workflows

    We connect returns ingestion, inspection, and refund signaling so returned items flow through Cin7 receiving with RMA traceability and credit notes land in ERP on time.

  5. 05
    Set up monitoring and alerting

    We instrument despatch lag, carrier rule drift, silent order failures, and stock-sync delays so you see fulfillment health in real time and act before SLAs slip.

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 order routing rules
Source / ownerCommerce and order management system
Maintained byOrder management and fulfillment ops
NotesCin7 executes routing based on configured location rules; ownership includes validating that rule drift is caught and updated when warehouse footprint changes.
DataAvailable stock and location inventory depth
Source / ownerCin7 Core
Maintained byWarehouse operations
NotesCin7 holds the live position after every receive, pick, and adjustment; commerce consumes published availability for catalogue and checkout; ERP balances are derived from Cin7 journals.
DataDespatch confirmations, tracking and labels
Source / ownerCin7 Core and carrier systems
Maintained byWarehouse fulfillment and carrier
NotesCin7 publishes despatch status and carrier tracking back to commerce; ownership includes ensuring tracking does not go stale if carrier feed breaks.
DataStock movements and warehouse transactions
Source / ownerCin7 Core
Maintained byWarehouse operations
NotesCin7 records all inventory movements; ERP journals them for accounting and balance-sheet reconciliation; ownership includes reconciliation tolerance and write-off policy.
DataReturns, RMA and refund instructions
Source / ownerCommerce order system initially; Cin7 RMA on receipt
Maintained byCommerce returns team and warehouse receiving
NotesReturns flow into Cin7 as RMAs; refund and disposition signals flow back to commerce and ERP; ownership includes reconciling physical returns against refund records.
DataException and unshippable item queues
Source / ownerCin7 Core
Maintained byFulfillment operations and customer service
NotesCin7 flags unshippable items and stock shortfalls; integration escalates them to a managed queue; ownership includes defining priority and approval path.
10 · Experienced integrator

Built this before

iWeb has built Cin7 Core integration for multi-channel and multi-location retailers. We understand how inventory, despatch and returns flow through Cin7 and how to connect it cleanly to commerce platforms and ERPs without creating reconciliation debt or silent failures.

We design location routing so orders flow to the right warehouse automatically and inventory allocation respects channel and geography constraints.
We build two-way stock sync that keeps commerce, Cin7 and ERP balanced daily without overselling or creating variance mysteries.
We establish exception handling so unshippable items, carrier failures and stock shortfalls surface in a managed queue with clear escalation.
We integrate returns workflows so physical returns trace through Cin7 RMA to refund completion without manual re-entry or lost records.
We instrument Cin7 so you see despatch lag, carrier rule drift, and silent order failures in real time before they affect customer experience.
11 · Before launch

What we test before launch.

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

Verify order routing rules direct test orders to the correct warehouse location based on inventory depth and geography.
Check that stock movements in Cin7 update commerce availability within the agreed sync window and no overbooking occurs across channels.
Confirm despatch events and carrier tracking flow back to commerce and appear on order status pages without manual intervention.
Test exception handling by placing an order for out-of-stock item and verify it queues for exception review rather than failing silently.
Validate that returned items flow into Cin7 as RMAs and refund instructions sync back to the ERP within SLA.
Confirm Cin7 stock movements create GL journals in the ERP daily and month-end reconciliation variance is within tolerance.
Test carrier fallback and label generation retry so that a carrier outage does not stall despatch completely.
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 queue in Cin7 without routing

If location rules are not configured or drift over time, orders queue in Cin7 but do not route to the correct warehouse. Despatch is delayed or sent to wrong location. Risk grows after a warehouse opens or closes without rule update.

Stock oversells across channels

If stock sync between Cin7 and commerce is slow or one-way only, stock can be sold twice across channels. Both fulfillment and returns are affected.

Despatch and tracking do not sync back

If despatch events or carrier tracking fail to flow back from Cin7 to commerce, order status pages go stale and customers receive no tracking updates. Risk is silent if no alert is configured.

Exceptions pile up unreviewed

Unshippable items, stock shortfalls, and carrier errors land in Cin7 but have no escalation path. Customer service does not know orders are stuck. Risk grows during peak season when queue depth is hard to monitor.

Stock reconciliation drifts from ERP

If Cin7 stock movements do not journal into the ERP, or if the sync is ad-hoc, month-end inventory reconciliation reveals weeks of untraced movements. Write-offs and adjustments grow.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about Cin7 Core integrations.

How do orders get from our commerce platform into Cin7?

Orders flow from your commerce platform via scheduled feed or webhook into Cin7 with line items, delivery address, and any location preference. Cin7 queues them for fulfillment and begins picking against available inventory. The integration handles order deduplication and retry logic so orders do not duplicate or get lost.

What happens if stock is not available in Cin7 for an ordered item?

If stock is unavailable, Cin7 marks the order or line as backorder and holds it in a queue. The integration can be configured to notify commerce and the customer automatically, or to escalate to your fulfillment team for approval. Backorder handling policy is set during setup and monitored for drift.

How does stock availability sync back to our storefront?

Cin7 publishes available inventory to commerce on a defined cadence (typically hourly or continuous), reflecting stock after every receive, pick, and warehouse adjustment. The integration preserves a small reserve pool if configured so that commerce always shows conservative availability and overbooking is prevented.

How do tracking and despatch confirmations reach the customer?

When an order is despatched in Cin7, despatch confirmation and carrier tracking number flow back to commerce automatically. Commerce then updates the customer's order status page and sends shipping notifications. If tracking fails to sync, alerts notify the fulfillment team so they can investigate before the customer notices.

What if we have multiple warehouses or drop-ship locations?

The integration configures location routing rules so orders route to the correct warehouse based on inventory depth, geography, and channel priority. If you operate drop-ship arrangements, those are configured as separate locations in Cin7 and routed accordingly. Rules are reviewed regularly to catch drift when warehouse footprint changes.

How are returned items handled?

Returned items flow from commerce into Cin7 as RMA records with a reason code and refund status. Warehouse staff receive and inspect the item; Cin7 records the disposition. Refund and credit instructions flow back to commerce and the ERP for processing. Traceability is maintained throughout so you can match physical returns to refund records.

How does Cin7 integrate with our ERP for stock reconciliation?

Warehouse transactions in Cin7 (receives, picks, write-offs, adjustments) create GL journal entries that flow to your ERP at configured intervals, typically daily. This keeps inventory balances synchronized and ensures month-end reconciliation is a verification step, not a week-long investigation. Reconciliation tolerance is set and monitored.

What happens if a despatch fails or an order sits in Cin7 too long?

The integration monitors order age, despatch lag, and carrier failures. If an order exceeds your SLA or a carrier integration breaks, alerts are sent to the fulfillment team. Unshippable items and exceptions land in a managed queue so they do not block other orders or go unnoticed.

Can we handle carrier selection rules and label generation?

Cin7 connects to major carriers for automatic label generation and rate selection. If your business uses regional or specialty carriers not natively supported, the integration can route those orders to a manual queue or feed them to a separate carrier system. Carrier rule drift is monitored so that rules stay current as your shipping footprint evolves.

How do we know if stock sync has broken without customers noticing?

The integration includes observability so you see stock-sync freshness, despatch lag, and silent failures in real time. Dashboards show order ingest rate, exception queue depth, and despatch performance. You can set thresholds so that stale inventory or unshipped orders trigger immediate alerts to the ops team.

What if we need to change location routing or stock reserve rules?

Location routing rules and stock reserve thresholds are configurable without redeploying the integration. Changes are tested in a sandbox environment first, then deployed to production. Observability captures the impact of rule changes so you can verify they work as intended.

How often should we reconcile Cin7 inventory against ERP balances?

The integration supports daily or real-time reconciliation through automated journals. We recommend a daily reconciliation to catch discrepancies early. A monthly physical audit of high-value or fast-moving lines should be planned to validate that Cin7 and ERP are in step. Tolerance thresholds are set during setup so minor variances do not trigger false alarms.

Next step

Have a Cin7 Core 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 →