Brightpearl integration for ecommerce fulfilment

Each channel (storefront, marketplace, B2B portal) publishes orders to an OMS or integration queue in a normalized format. iWeb builds the bridge from that queue into Brightpearl so all orders arrive with customer address, line items, SKU references, and fulfillment preferences. Brightpearl then applies routing rules to assign the order to a warehouse.

If the assigned warehouse is out of stock, Brightpearl can reroute the order to an alternate warehouse or hold it in an exception queue. The exception queue alerts fulfillment teams with context (why it failed, which warehouse has stock, estimated delay). Without this visibility, orders sit silent and dispatch is delayed.

Once a label is generated in Brightpearl and the order is handed to a carrier, the tracking number is captured. iWeb ensures this tracking data flows back to your commerce platform and customer accounts in real-time so customers see their tracking link without delay.

Stock is pulled from your ERP into Brightpearl to inform allocation and picking. As orders are picked and shipped, stock movements flow back to ERP so your perpetual inventory stays accurate. Without this synchronization, ERP stock reports lag reality and overselling becomes likely.

Returns flow from your commerce platform or OMS into Brightpearl with the original order reference. Brightpearl generates an RMA number and receipt instructions. Once the item arrives at the warehouse and is processed, Brightpearl triggers stock restoration and a refund authorization flows to ERP and back to the customer.

Carrier selection rules (service level, zone, weight thresholds), label formats, and manifest requirements are configured in Brightpearl. When carriers change or service levels shift, the rules are updated centrally. iWeb ensures these changes are documented and tested so no orders use outdated rules.

If the carrier API times out or rejects a request, Brightpearl typically retries automatically. However, if the failure persists, the order hangs in a dispatch queue waiting for manual intervention. iWeb builds observability so these failures surface immediately so fulfillment teams can resolve them before customers complain about missing tracking.

Brightpearl supports custom routing rules based on warehouse location, service level, and inventory availability. iWeb can build business logic that routes orders to the nearest warehouse or the fastest fulfillment option. This requires mapping customer postcodes to fulfillment zones within Brightpearl's configuration.

Marketplace returns are initiated on the marketplace and flow into your OMS or commerce system, then into Brightpearl. iWeb ensures marketplace-specific return requirements (restocking fee, condition assessment) and seller SKU references are preserved so Brightpearl returns the item to the correct location and the marketplace refund is authorized correctly.

If Brightpearl is down, orders queued for dispatch cannot be allocated to a warehouse. iWeb designs fallback buffering so orders do not back up in commerce; instead, they wait in a resilient queue. Once Brightpearl recovers, orders are reprocessed and dispatch resumes without data loss.

iWeb builds dashboards and alerting so fulfillment teams see exceptions in real-time: out-of-stock orders, address validation failures, carrier rejections, and unshipped orders by age. Each exception includes context and suggested actions so teams can resolve them quickly without manual investigation.

iWeb runs test orders from each of your sales channels through Brightpearl to verify orders are routed to the correct warehouse, labels are generated for all carriers, tracking flows back to commerce, and returns are processed end-to-end. We validate that stock is reserved, dispatched, and reconciled correctly in ERP.

Orders must include valid customer address, line items with correct SKU references, quantity, and delivery postcode. Fulfillment preferences (express, standard, gift wrap) and any marketplace-specific metadata must also be present. iWeb validates orders before they enter Brightpearl so incomplete orders are rejected with clear feedback rather than failing silently.

Stock adjustments are typically made in your ERP or Brightpearl depending on where the issue was discovered. iWeb ensures adjustments flow to both systems so the stock in Brightpearl and the financial records in ERP stay aligned. Without this, fulfillment allocation becomes unreliable.