Benefits of the Joolan x Shippingbo connector
Save time on every order
Shippingbo reduces data re-entry, intermediate files and manual checks between Fastmag, logistics and your other tools. Your teams move faster with less friction.
Make stock data more reliable for better execution
Shippingbo helps maintain a cleaner view of logistics stock and synchronise the relevant data according to your organisation. You limit discrepancies that cause stockouts, delays and unnecessary trade-offs.
Run your B2B, B2C and marketplace flows with greater confidence
As channels multiply, Shippingbo helps structure execution around clearer rules. You maintain a more organised operation even with several order flows.
Handle the workload more effectively as activity accelerates
Volume peaks, new channels, new sites and exports: Shippingbo helps you maintain clean execution without multiplying in-house tools, custom developments and workarounds.
What is synchronised between Fastmag and Shippingbo
Synchronization is automatic. Some behaviors depend on order status and enabled options
| Data | Direction | Trigger and/or frequency |
|---|---|---|
| B2C orders | Joolan Shippingbo | Automatic retrieval from the sales source |
| Order to send to the ERP | Shippingbo Joolan | At status "To prepare" or "Shipped" |
| B2B orders entered in the ERP | Joolan Shippingbo | On entry or in regular batches |
| Product references / logistics data | Joolan Shippingbo | On creation, update or in batches |
| Stock | Joolan Shippingbo | According to defined frequency |
| Inbound receipts | Joolan Shippingbo | According to the defined process |
Connection steps: Connect Joolan to Shippingbo in just a few steps
-
1.Define the project scope upfront with an integrator
Define the flows to enable: B2C orders, B2B orders, catalogue, stock, inbound receipts and returns.
-
2.Define the master system for each data type
Catalogue, stock, orders and shipments: avoid having the ERP and Shippingbo modify the same data at the same time.
-
3.The integrator develops the connector
Development by an integrator with in-depth knowledge of Shippingbo flows
-
4.Test and go live with key business scenarios
Cancellation, partial shipment, returns, replenishment, B2B orders and multiple locations: validate the use cases that really matter before deployment.
The limitations of Joolan without Shippingbo
Without Shippingbo
- Prepare without data re-entry: Too much back-and-forth between tools
- Keep stock up to date: More fragmented tracking
- Handle more volume: More fragile processes
- Track inbound receipts and shipments: Scattered visibility
- Evolve logistics rules: Hard for operational teams to understand
- Give Ops visibility: Scattered information
With Shippingbo
- Workflows centralised in Shippingbo
- Stock changes sent back automatically
- More structured execution
- Unified workflow management
- Execution managed in a dedicated tool
- Clearer view of operations
Reliable, available and secure technology
-
99.99% uptime
and proven cloud infrastructure
-
Geo-replication
and real-time synchronization
-
Continuous updates
without downtime
-
GDPR compliance
and regular audits
-
Proven cloud infrastructure
and regular audits
FAQ - Frequently asked questions
What is the Shippingbo Joolan connector used for?
The connector automatically moves relevant data between Joolan and Shippingbo to execute logistics more cleanly. Joolan remains in its ERP role. Shippingbo takes over logistics operations orchestration: orders, stock, inbound receipts and shipments according to the enabled scope.
What data is synchronised between Joolan and Shippingbo?
Joolan sends orders, expected receipts and products to Shippingbo. Shippingbo sends shipments, receipts and stock changes back to Joolan. A catalogue export is also sent once a day to check the stock snapshot.
How often is data sent back to Joolan?
Outgoing Shippingbo-to-Joolan workflows use differential exports every 10 minutes for shipments, receipts and stock changes. The product catalogue is sent once a day at 23:00.
Are manual exports required for the connector to work?
The connector is specifically designed to avoid reliance on repeated manual exports. Exchanges use FTPS with .csv files, for both inbound and outbound workflows according to the defined configuration.