The BOL.com Inbound (FBB) connector pulls your Fulfilment by bol (FBB) replenishments from BOL.com into the app as inbound transfer orders and creates a shipment request for each one. As bol receives the goods at its fulfilment centre, the app posts the received quantities as receipts. The connector only reads from BOL.com and never sends data back to it.
With this connector, you can:
- Pull announced FBB replenishments into the app as transfer orders every 5 minutes.
- Create a shipment request for each replenishment, with bol’s load carrier labels and pick list attached.
- Cancel the transfer order in the app when the replenishment is canceled in BOL.com.
- Mark replenishments as fulfilled automatically when you ship to bol without a connected 3PL.
- Post the quantities bol receives as receipts against the BOL.com FBB location.
Setup
Before you begin, make sure you have:
- The connector turned on for your organization. This connector is in beta, so submit a support request to turn it on.
- A BOL.com seller account that uses Fulfilment by bol (FBB).
- A Client ID and Client Secret for the BOL.com Retailer API. To create them, log in to the BOL.com Seller Dashboard and go to API Instellingen (API settings).
- A location in the app for each warehouse that ships replenishments to bol, with the same postcode that bol shows on the pickup appointment. The app matches each replenishment to its source location by this postcode.
- Your products in the app, with each BOL.com offer’s reference set to the product’s SKU in the app. Replenishments list items by EAN only, so the app uses the offer reference to find the SKU.
To connect BOL.com Inbound (FBB):
- Navigate to Integrations in the app.
- Click Add Integration, and then select BOL.com Inbound (FBB).
- Enter your BOL.com API Client ID in the Client ID field.
- Enter your BOL.com API Client Secret in the Client Secret field.
- Click Connect.
- After you connect, toggle on the flows you want to use: Pull inbound replenishments from BOL.com and Pull receipt information from BOL.com.
Settings
| Setting | Description | Options/Default |
|---|---|---|
| Pull inbound replenishments from BOL.com | Pulls FBB replenishments as inbound transfer orders and creates a shipment request for each one. This setting also creates the Bol.com FBB location. | On/Off. Default: Off |
| Exclude replenishments created before this date | Pulls only replenishments created after this date. | Optional. Default: the date you created the integration |
| Pull shipping labels from BOL.com | When on, each shipment request waits in Pending Shipping Label while the app attaches bol’s load carrier labels and pick list, and then moves to Ready for Fulfillment. When off, shipment requests go straight to Ready for Fulfillment. Turn it off only if you create bol’s labels yourself. | On/Off |
| Auto-fulfill replenishments when no 3PL is connected | Marks the shipment as fulfilled when the replenishment’s source location isn’t linked to a fulfillment integration. Turn this on if you ship to bol yourself, so the app creates the arrival and receipts can post. | On/Off. Default: Off |
| Pull receipt information from BOL.com | Posts the quantities bol receives to the matching arrival in the app as receipts. | On/Off. Default: Off |
| Exclude receipts for inbound shipments recorded before this date | Posts receipts only for arrivals created in the app after this date. | Optional. Default: the date you created the integration |
Flows
| Flow | Direction | Notes |
|---|---|---|
| Locations | BOL.com → Pipe17 | BOL.com doesn’t list its fulfilment centres, so the app creates one location named Bol.com FBB that every replenishment is sent to. Each transfer order carries the actual fulfilment centre address. Runs every 5 minutes while Pull inbound replenishments from BOL.com is on. |
| Transfer orders | BOL.com → Pipe17 | Runs every 5 minutes. Pulls replenishments with the status Announced. The source location is matched by pickup postcode, and quantities are in units. If the postcode doesn’t match a location, or an EAN doesn’t match a SKU, the transfer order is created as a draft with an exception. Replenishments canceled in BOL.com in the last 30 days cancel the transfer order in the app. |
| Shipment requests | Pipe17 → your 3PL | The app creates one shipment request per transfer order for the 3PL linked to the source location. With Pull shipping labels from BOL.com on, the app attaches the transport and warehouse load carrier labels and the pick list once bol assigns load carriers. Labels that aren’t available yet don’t hold up the shipment request. |
| Fulfillments | Pipe17 | Created by the connector only when Auto-fulfill replenishments when no 3PL is connected is on and no other integration fulfills from the source location. Otherwise, your connected 3PL reports the fulfillment. Uses bol’s track and trace codes when they’re available. |
| Receipts | BOL.com → Pipe17 | Runs every 5 minutes for each open arrival at Bol.com FBB. Posts only the quantity received since the last receipt. Arrivals marked received in the last 30 days are checked again for late quantities. If bol lowers a received quantity, the app doesn’t post a negative receipt. |
| FBB inventory | Not supported | The connector doesn’t pull FBB stock levels. On-hand at Bol.com FBB reflects received quantities only and doesn’t go down when bol ships FBB orders. |
| Updates to BOL.com | Not supported | The connector doesn’t create or change replenishments in BOL.com. |
Troubleshooting
A transfer order is a draft with an exception about an unmapped source postcode
No location in the app has the postcode from bol’s pickup appointment. Add or update the source location with that postcode, and then run the Pull inbound replenishments from BOL.com by replenishment id action for the replenishment. Replenishments you deliver to bol yourself have no pickup address, so the app can’t match a source location for them. To learn more, see Getting Started with Locations in Pipe17.A transfer order is a draft with an exception that lists EANs with no SKU
No BOL.com offer links those EANs to a SKU in the app. In BOL.com, set each offer’s reference to the product’s SKU in the app, and then run the Pull inbound replenishments from BOL.com by replenishment id action again.The connection fails or every request returns an authorization error
The Client ID or Client Secret is wrong or was deleted. Create new API credentials in the BOL.com Seller Dashboard under API Instellingen, and then update them in the connection settings.No receipts post for a replenishment
Receipts post against an arrival, and the app creates the arrival only after the shipment request is fulfilled. Check that your 3PL fulfilled the shipment request, or turn on Auto-fulfill replenishments when no 3PL is connected if you ship to bol yourself. Also check that Pull receipt information from BOL.com is on. To post receipts for one replenishment, run the Pull receipts from BOL.com by replenishment id action.A shipment request has no labels
Bol assigns load carriers after a replenishment is announced. If the shipment request moved to Ready for Fulfillment before that, the app doesn’t add the labels later. Download them from the BOL.com Seller Dashboard.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the platform page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
We’re here to help you succeed with your operations.
Comments
0 comments