01
Automated label generation
Orders that reach ready-to-ship produce a DX label and any customs paperwork without a human opening a portal.
Outcome: seconds per parcel instead of minutes.
DX integration specialists
DX API integration and platform bridging
We connect DX to the systems your business already runs on — accounting, ERP, warehouse, CRM and courier platforms — so that labels, tracking events and proof of delivery move between them without manual intervention.
Fixed-scope engagements, delivered by UK-based integration engineers. Documentation and source code handed over on completion.
- ✓Consignment API
- ✓Freight & secure services
- ✓Tracking write-back
What we can connect DX to
DX carries your parcels. The systems around it — your storefront, ERP, warehouse and order management — each hold part of the same shipment data. Our role is to make one the source of truth and keep the rest aligned, through the DX API, and a bridging layer where an order source has no usable interface of its own.
Ecommerce platforms
Pull ready-to-ship orders from your storefront, generate DX labels and customs data, and write tracking back to the order so the customer is notified automatically.
Shopify, WooCommerce, Magento, BigCommerce
Warehouse and 3PL
Trigger DX label creation from the WMS pick and pack step and return the tracking number and weight to the shipment record.
Mintsoft, Peoplevox, Despatch Cloud, in-house WMS
ERP and order management
Take despatch instructions from the ERP or OMS, book DX services against them and post the shipping cost back for margin reporting.
NetSuite, Microsoft Dynamics, Linnworks
Marketplaces
Meet Amazon and eBay despatch SLAs by generating DX labels directly from marketplace orders with valid tracking inside the required window.
Amazon SP-API, eBay
Other carriers
Apply service-selection rules across DX and your other carriers by weight, value, destination and promised date, with a manual override.
Royal Mail, DPD, Evri, DHL, UPS, FedEx
Bespoke and legacy systems
An in-house despatch desk or a legacy order system connected to DX through a documented, queued interface.
SQL Server, SFTP, SOAP, CSV drop
Common DX integration use cases
Each is a defined, testable data flow rather than an open-ended development project.
02
Service selection rules
Weight, value, destination and the promised delivery date choose the DX service automatically, with a manual override when needed.
Outcome: the right service every time, lower carrier spend.
03
Tracking write-back
Tracking numbers and DX status events flow back to the order so customer notifications fire without anyone touching them.
Outcome: fewer where-is-my-order enquiries.
04
Manifest and end-of-day
Consolidated DX manifests are produced and filed automatically at the collection cut-off.
Outcome: no missed collections.
05
Returns labels
Inbound DX labels are issued on approval and matched back to the original shipment on receipt.
Outcome: returns processed the same day.
06
Cost reconciliation
Booked DX costs are posted against orders so shipping margin is visible per channel and per SKU.
Outcome: shipping stops being a black box.
How a DX API integration is delivered
Four stages, fixed scope agreed before any code is written. Typical delivery for a single-system integration is two to four weeks.
Stage one
Discovery and data mapping
We document the systems involved, the direction of each flow, and every field that must move — including the awkward ones such as tax, discounts and multi-currency.
Output: written integration specification.
Stage two
Fixed scope and estimate
The specification becomes a fixed-price proposal with a delivery schedule and defined acceptance criteria. No time-and-materials open ends.
Output: costed scope for sign-off.
Stage three
Build and testing
Development against a DX development or sandbox environment and a sandbox of the destination system, with your own data used for acceptance testing.
Output: tested integration and test evidence.
Stage four
Go-live and handover
Controlled cutover with monitoring in place, followed by handover of code, credentials and documentation, and a period of hypercare support.
Output: live integration, owned by you.
Have a DX data flow in mind? We will tell you what it takes before you commit.
Request a scopeDX API bridging when there is no direct connector
A generic connector works until the moment your setup differs from the demo — a custom field, a second warehouse, a system on the other end with no API at all. At that point the integration has to be built around your actual data, not a vendor's assumption of it.
That layer normalises data formats, holds a queue so neither platform is overwhelmed, authenticated the way DX expects — Account credentials — and records every transaction so a disputed record can be traced end to end. It also isolates you from change: when DX deprecates an API version, only the bridge is updated.
If there is no usable interface at all, the fallback is a flat-file exchange, a direct database connection, or a small REST wrapper we write and host ourselves — whichever fits what is actually there.
Included in every bridge we build
- →Error handling with alerting when a transfer fails
- →Automatic retries that respect the carrier API rate limits
- →A transaction log for tracing any individual shipment
- →Idempotency so a repeated event cannot duplicate a label
- →Field-level mapping documentation you can hand to any developer
- →A staging environment that mirrors production
DX integration FAQs
A single-direction integration between DX and one order source is typically delivered in two to four weeks, including discovery, field-level mapping, build against the DX sandbox, acceptance testing with your own orders and supported go-live.
Yes. The integration books against your own DX account and contract, and service-selection rules are configured to match how your operation already ships — by weight bands, destination zones, value thresholds and promised dates.
Carrier APIs are versioned and change on their own schedule. Integrations under a support agreement are reviewed each release cycle and migrated ahead of deprecation dates; for handed-over work the version dependencies are documented so your team can plan.
You do. Source code, credentials, configuration and documentation are handed over on completion, and there is no licence fee for continuing to use it. Monitoring and change support are available under a separate agreement.
Other platforms we integrate
Each platform has its own integration guide covering authentication, available endpoints and typical data flows.
