Systems and integrations
Store-to-3PL integration, tested before go-live.
Keep selling where you sell now while the data moves in the background. A custom integration can always be built.
Systems integration
How data moves between your systems and the warehouse.
You keep selling where you sell now. Orders reach the warehouse, and stock levels, tracking numbers and return results come back to your systems.
Choose a data flow
Lines, address and delivery method reach the warehouse and wait for picking.
Possible exchange methods, matched to your systems
- API or pluginAutomatic exchange where your platform allows it.
- EDIStandard messages, common with retail chains and larger ERP systems.
- Files (CSV, SFTP)Structured file exchange where full integration is not yet needed.
- Custom integrationWhere no ready connection fits, we build one around your systems.
General diagram of the working model, not a list of live integrations. The specific connection is confirmed by testing during onboarding, and its scope depends on your systems.
Our approach
We assess your systems case by case, and a custom integration can always be built. This page explains what proving a connection involves. We name integrations publicly once they are proven.
Data flows
What moves, in which direction.
Whatever the technology, these are the conversations your systems and the warehouse need to have.
| Data | Direction | What it carries | What goes wrong without it |
|---|---|---|---|
| Orders | You to ShipRevo | Order number, lines and SKUs, delivery address, shipping method, handling notes | Mismatched SKU codes leave orders stuck, or the wrong item gets packed |
| Dispatch confirmation | ShipRevo to you | Order status and carrier tracking reference | Customers ask where the parcel is and nobody can answer |
| Stock | ShipRevo to you | Available quantity, kept apart from blocked and quarantined items | Your shop sells items that are sitting in quarantine |
| Inbound notices | You to ShipRevo | Expected date, SKUs, quantities, lot and expiry where tracked | Goods arrive with nothing to count them against |
| Returns | Both directions | Order or RMA reference, SKU, recorded condition, outcome | You refund blind, or stock is released before anyone checked it |
| Reports | ShipRevo to you | Count differences, exceptions, activity behind the invoice | Problems surface at stocktake and invoices cannot be checked |
How each flow travels, through a tested connection, a custom integration or a structured file exchange, is agreed per client during set-up and written down.
Before go-live
What a 3PL integration test looks like.
One clean sample order says little about a connection. The cases below are the ones that tend to cause trouble in live use. They are part of the pilot.
- 01
Map the fields
We agree which system is the master for stock, which code identifies a SKU, and how each field and status translates. The mapping is written down.
Both, with whoever administers your systems.
- 02
Send awkward orders
Unknown SKU, multi-line order, a long delivery address, a cancellation after release, an order with handling notes. We check what arrives, and what happens when it should be rejected.
You: send. ShipRevo: check.
- 03
Compare stock both ways
Physical count, warehouse record and your system are compared after inbound, after dispatch and after a return. Blocked and quarantined items must not appear as available.
ShipRevo: counts and compares. You: confirm.
- 04
Run returns through
A test return per outcome, so you can see what your system receives in each case and what it does with it.
ShipRevo: runs. You: check on your side.
- 05
Agree the fallback, then sign off
If the exchange fails, who notices, who gets told, what gets re-sent and how duplicates are avoided. Written down before go-live, along with your sign-off.
Both.
What we ask for
What helps us assess your set-up.
You can name your systems in the quote form. Naming them does not commit you, and it lets us give you a clear answer earlier.
Your systems
- Your sales platform or platforms
- ERP or WMS, if you run one
- Anything else that touches orders or stock, including spreadsheets
- Who administers each one
Access for testing
- A test environment or test account, where one exists
- Documentation for the connection or export you plan to use
- A sample export of real order and stock data, with customer details removed
Decisions on your side
- Which system is the master for stock
- Which order statuses release an order to the warehouse
- How cancellations after release are handled
- Who signs off the test
Questions
What buyers ask about 3PL integrations.
Which platforms are you integrated with?
We assess your systems case by case and name integrations publicly once they are proven. Where no ready connection fits, a custom integration can always be built. Tell us what you use and we will assess it for your case.
We run on spreadsheets. Is that a problem?
Not necessarily. A structured file can work if the columns are fixed and someone owns the file. If your volumes or order mix make that too risky, we will tell you before go-live and propose a connection instead.
How will we know our stock levels?
That is agreed during set-up: stock data passed to your system, reports, or both. We describe what is available in your case and test it with you before go-live.
What happens to our customers’ data?
We work with what shipping and returns require. Processing terms belong in your agreement with us. The privacy policy covers data sent through this website, including the quote form.
Next step
Tell us what you run.
Name your sales platform and any WMS or ERP in the form. We will tell you how we would connect it and what we would need to test.