Unipart Logistics Fulfilment Integration Specialists

Confirmed orders are sent via API or EDI feed to Unipart's WMS with customer, item, quantity, address and special instructions. iWeb defines which order statuses trigger transmission and ensures all required fields are validated before dispatch to the warehouse.

Unipart flags the order as unfulfillable (out-of-stock, address fault, damaged goods). iWeb routes the exception to your operations or customer service team immediately and defines who decides whether to cancel, amend or retry the order. Customer notification is sent according to your policy.

When Unipart packs and ships an order, the despatch data (items, carrier, tracking) flows back via API. iWeb maps this to your order record and triggers customer email notifications so they receive tracking immediately.

If an order is split across multiple Unipart locations or ships in multiple parcels, iWeb aggregates the despatch events and sends a consolidated or multi-parcel notification to the customer. Each parcel has its own tracking reference and status.

iWeb syncs warehouse picks, returns, shrinkage and stock-take adjustments from Unipart back to ERP at defined intervals. Stock is reserved on order confirmation and committed when despatch is confirmed, preventing oversells.

Returned items arrive at Unipart, are logged in the WMS, and iWeb ensures the return is linked to the original order and communicated back to your commerce platform and ERP. Refund decisions (restock, scrap, resale) are clarified upfront so returns do not stall.

iWeb builds dashboards showing order-to-despatch lag, unshipped backlog by age, and exception queues. Alerts trigger if orders exceed SLA without confirmation, so the team can investigate Unipart hold-ups or customer service issues.

iWeb implements retry logic and dead-letter queues so failed orders are not lost. If despatch feeds lag beyond SLA, alerts notify operations. Temporary outages trigger a fallback: orders may be queued locally until Unipart recovers, or rerouted to another warehouse if available.

Unipart flags addresses that fail delivery validation and carrier rejections (e.g., too heavy, restricted postcode). iWeb routes these exceptions to a named team for correction; the customer is contacted with new delivery options or timeline. No order is abandoned silently.

Despatch confirmations from Unipart feed ERP immediately after Unipart confirms the shipment. iWeb ensures the invoice is triggered at this point, not at order placement, so revenue recognition aligns with actual fulfillment.

Yes. iWeb can define routing rules based on product type, location, order size or customer segment. Orders route to the appropriate Unipart warehouse automatically, with exception handling if the preferred location cannot fulfill.

iWeb pulls despatch confirmations immediately after warehouse confirmation, so tracking is available within minutes of packing. Stock movements may be batch-fed at defined intervals (e.g., hourly). Backlogs and exceptions are monitored in real time with alerting.

iWeb clarifies Unipart's peak SLAs upfront (e.g., order acceptance lag, pick timelines). During peak, orders queue locally if needed but are logged and communicated to the customer. iWeb monitors SLA breach and escalates if delays risk missing promised delivery windows.

This is defined upfront by iWeb. Typically, Unipart holds the order if customer-initiated cancellation arrives after picking has begun, and customer service confirms the final decision. iWeb ensures communication flows between warehouse, customer service and ERP so decisions are logged.