Every Bol order carries a delivery date Bol holds you to. Orders stuck in a separate integration's queue put it at risk before anyone picks.
When stock reaches Bol on a different schedule than your other channels, offers show out of stock with units on the shelf, or oversell.
You ship FBR orders and Bol ships FBB orders. Finance reconciles each stream against the ERP separately, and the gaps surface at month-end close.
| iPaaS & Custom Builds | Legacy OMS | Pipe17 | |
|---|---|---|---|
| Native API-First Connectivity | ✅ | ❌ | ✅ |
| Pre-Built Commerce Connectors | ❌ | ❌ | ✅ |
| Custom Integration Mappings | ✅ | ❌ | ✅ |
| Advanced Order Orchestration | ❌ | ✅ | ✅ |
| Unified Inventory Management | ❌ | ✅ | ✅ |
| Exception Management & Alerts | ❌ | ❌ | ✅ |
| Real-Time Ops Dashboard | ❌ | ❌ | ✅ |
| Rapid Implementation | ❌ | ❌ | ✅ |
| Easy to Add / Swap Channels | ❌ | ❌ | ✅ |
| Developer-Free Customization | ❌ | ❌ | ✅ |
| Low Total Cost of Ownership (TCO) | ❌ | ❌ | ✅ |
FBR orders route to your warehouse or 3PL, and Bol's delivery date stays on each order. When they ship, Bol gets track and trace.
Pipe17 pushes available stock to the Bol offers you fulfill, totaled across your warehouses or from one location you choose. Prices follow from your catalog.
FBR and FBB orders land in Pipe17 marked by fulfillment method. FBR returns, and FBB returns if you choose, join one returns flow.
is better with
The managed Bol connector ties your Bol seller account to Pipe17's Order Operations Platform. Orders arrive with lines resolved to your SKUs and the fulfillment method marked, and the ones you fulfill route to your warehouses and 3PLs. Pipe17 sends track and trace to Bol, pushes stock and prices to the offers you fulfill, and mirrors handled returns into Pipe17. Bol keeps the storefront. Pipe17 runs the operation behind it.
Yes, Pipe17 supports both Bol fulfillment methods: FBR (fulfillment by retailer, where you ship) and FBB (fulfillment by Bol, also called Logistics via Bol or LVB, where Bol ships). Pipe17 sends FBR orders through order routing to your warehouse or 3PL. FBB orders stay visible for reporting and reconciliation but are not routed, so nothing ships twice. Stock and price updates apply only to offers you fulfill.
Each Bol order arrives with its order and line details, SKU and European Article Number (EAN), prices and discounts, expected delivery date, fulfillment method per line, and customer and shipping address. New and updated orders reach Pipe17 continuously. Bol exposes roughly the last 3 months of order history, and Pipe17 can backfill from any date in that window or pull specific order IDs on demand.
When an order you fulfill ships, the fulfillment lands in Pipe17 with carrier and tracking, and Pipe17 confirms it to Bol with the matching Bol carrier code and track and trace. Split shipments confirm separately. Pipe17 tracks each confirmation until Bol accepts it, and a rejected one, for example with an unrecognized carrier code, lands in Exception Resolution for your team.
Pipe17 pushes the available quantity for each SKU to the matching Bol offer you fulfill, totaled across your active locations or from one location you designate. Prices push the same way from your Pipe17 catalog, in euros with value-added tax (VAT) included. Titles, descriptions, and images stay managed in Bol. Inventory Visibility holds Bol to the same stock count as your other channels, the count Pipe17 uses to prevent overselling.
Pipe17 pulls returns Bol has handled, each with the original order, SKU, quantity, reason, and tracking where Bol has it. Open return requests wait until Bol decides them. You choose which dispositions to mirror, separately for orders you fulfill (FBR) and orders Bol fulfills (FBB). With return write-back on, Pipe17 reports returns received at your own facility back to Bol, and mirrored returns run through Pipe17 Returns Management.
Yes, Pipe17 pulls each fulfillment by Bol (FBB) replenishment you announce to a Bol fulfillment center as an inbound transfer order, attaches Bol's load carrier labels and pick list, and issues the shipment request to whichever warehouse or 3PL sends the goods. What Bol receives posts back as receipts. It is the same pattern Pipe17 runs for Amazon FBA inbound.
Yes, Bol runs alongside Amazon, Shopify, and your other channels as one more order source on the Pipe17 Network. A Bol order you fulfill gets the same routing rules, inventory, and exception handling as an Amazon or Shopify order, from the same warehouse and stock count. For 3PLs serving European brands, Bol fulfillment becomes one more service.
In your Bol seller dashboard, open the API settings and create Retailer API credentials. Enter the Client ID and Client Secret in Pipe17, then choose which flows and fulfillment methods to sync. Pipe17 manages the API token from there. Set a start date to limit which orders sync, or SKU filters to roll out a subset first. Pipe17 builds and runs the connector, and your developers maintain nothing.