DeliveryMatch

BizBloqs × DeliveryMatch

THE RIGHT CARRIER, DECIDED ON REAL DATA

Rate shopping only works when the numbers are real. Feed a selection engine an estimated weight and a guessed box size and it will confidently pick a service that invoices you for something else next month.

BizBloqs sends DeliveryMatch what the packing station actually measured, and prints the label the engine selects.

Book a demo Visit DeliveryMatch

Explore DeliveryMatch

Visit DeliveryMatch

IS THIS YOU?

Who this DeliveryMatch integration is for

You negotiated good rates. You are still paying surcharges on parcels nobody weighed.

You have several carrier contracts and want each shipment on the cheapest fitting one.
Surcharge invoices for weight or dimensions are a recurring irritation.
You promise delivery dates online and want the warehouse to honour them by rule.

WHAT IS DELIVERYMATCH?

CARRIER SELECTION AGAINST YOUR OWN CONTRACTS

DeliveryMatch compares your carrier contracts per shipment and selects on cost, speed or the delivery promise you made to the customer.

The quality of that selection is a direct function of the shipment data behind it — which is a warehouse output, not a webshop field.

NO DECISION AT THE PACKING TABLE

The call happens while the packer closes the box. The selected service comes back with the label and prints in the same movement.

Where a lane fails, a fallback service takes over automatically; a carrier outage is not something a packer should have to solve.

OUR SOLUTIONS

SMEGet off paper. Get in control.SME+Multi-channel, multi-warehouse, still fast to change.EnterpriseMulti-entity, deeply integrated, fully auditable.

WHAT CHANGES ONCE DELIVERYMATCH AND BIZBLOQS ARE CONNECTED

Shipments, selection results, labels and status move between BizBloqs and DeliveryMatch as parcels are packed.

Selection on measured weight and size

Weight and dimensions are captured at the station and sent with the request, so the engine selects on facts rather than on catalogue estimates.

Cheapest, fastest or promise-driven

Your selection criterion is a rule: cheapest fitting service, fastest, or whatever honours the promise shown at checkout.

Label printed in the packing flow

The chosen service and its label return in the same interaction, so selection costs no floor time at all.

Fallback service per lane

If the preferred carrier is unavailable, the configured fallback is used automatically and the packer keeps packing.

Tracking and status on the order

Tracking codes and status updates are written back on the order and forwarded to the sales channel.

Manifest closed per carrier

End of day closes per carrier, so the driver handover is a scan and the administration is already done.

This is what your DeliveryMatch setup looks like from day one

See it on your own order flow. Thirty minutes, screen share, no slide deck — or tell us where it hurts today and we will tell you honestly whether we can fix it.

Book a demo Talk to sales

Carrier integration

How the DeliveryMatch integration works

DeliveryMatch picks the best carrier and service per shipment against your own contracts. BizBloqs supplies the physical facts it needs — real weights, real dimensions, real colli — because rate shopping on estimated data produces the wrong answer and a surcharge later.

DeliveryMatch — carrier selection and booking

REST API with rate shopping, service selection and label retrieval

At packing, BizBloqs sends the shipment to DeliveryMatch and receives the selected carrier, service and label. Where you want the customer to choose, the delivery options can also be resolved earlier in the order flow and honoured downstream by the warehouse. Tracking codes and status updates come back onto the order, and the end-of-day manifest closes per carrier.

What you need

A DeliveryMatch account with your carrier contracts loaded
API credentials from your DeliveryMatch environment
Scales and, where relevant, dimensioning at the packing stations
Agreed selection criteria: cheapest, fastest or promise-driven

Which messages are exchanged

This is the standard message set between BizBloqs and DeliveryMatch. Empty fields mean that message is not exchanged in that direction by default; optional rows depend on your modules, licence and process.

DeliveryMatchBizBloqs WMS

Into BizBloqs

Out of BizBloqs

Carrier contracts / servicescore

Into BizBloqsAvailable carriers, services and product codes

Shipment announcementcore

Out of BizBloqsParcel, address, weight, dimensions, service

Labelscore

Into BizBloqsLabel (PDF/ZPL) printed at the packing station

Tracking codescore

Into BizBloqsTrack & trace code per parcel

Status updatesoptional

Into BizBloqsCollected, in transit, delivered, exception

Multi-collo shipmentscore

Into BizBloqsOne label per colli in a shipment

Out of BizBloqsColli split per order

Customs documentsoptional

Into BizBloqsCommercial invoice and CN22/CN23 where required

Out of BizBloqsCustoms data per line

Returnsoptional

Into BizBloqsReturn label / return portal reference

Out of BizBloqsReturn announcement

Pickup / manifestoptional

Into BizBloqsManifest confirmation

Out of BizBloqsEnd-of-day close per carrier

This is our standard integration. An empty field means that message is not exchanged in that direction by default. Integrations can be modified or extended customer-specific through workflows.

Track & trace: from label to delivered

A tracking code is only worth something once it reaches the person asking about the order. This is the full relay chain between DeliveryMatch, BizBloqs and the system your order came from.

The relay chain

1. Shipment booked
When the packer confirms the shipment, BizBloqs announces the parcel to DeliveryMatch: address, weight, dimensions, service and the order reference. The shipping rule decides carrier and service, so the packer never picks one from a list.
2. Label returned
DeliveryMatch returns the label (PDF or ZPL) and the parcel number. The label prints at the pack station inside the pack flow. A multi-collo shipment returns one label per colli, each with its own parcel number.
3. Tracking code stored
The track & trace code is stored on the shipment in BizBloqs, per colli, alongside the carrier and service actually used. From this moment the code exists in the WMS and can be relayed onwards.
4. Status updates by webhook
DeliveryMatch pushes status changes — collected, in transit, out for delivery, delivered, exception — to BizBloqs over a webhook. No polling, so the status in the warehouse is the carrier's status, not a cached guess.
5. Proof of delivery
Where the carrier supplies it, the proof of delivery — signature, delivery photo, timestamp and receiver name — is attached to the shipment. Exceptions such as a refusal or a failed delivery arrive on the same channel and stay visible instead of disappearing.
6. Relayed to the order source
BizBloqs relays the tracking code and the delivery status back to whichever system the order came from, and onward to the customer-facing channel. The warehouse is the single point where shipment truth is collected, and every downstream system reads the same value.

Where the tracking code is relayed to

BizBloqs holds the shipment truth and pushes it outward. Which of these run depends on which systems you have connected.

ERPThe shipment confirmation carries the carrier, the parcel numbers and the tracking codes, so the ERP can invoice and answer a where-is-my-order question without opening the WMS.
WebshopThe fulfilment posted to the webshop includes the carrier and the tracking code, which triggers the platform's own shipping confirmation and fills the my-account order page.
Marketplace channelMarketplaces score you on it, so the tracking code goes back on the channel's own shipment message inside the promised window, per colli where the channel supports it.
Customer notificationWhoever owns the customer relationship sends the notification: the carrier, the webshop or your ERP. BizBloqs supplies the code; it does not send marketing mail on your behalf.
Warehouse and service deskIn BizBloqs the shipment shows its current status and history, so a service desk can trace an order end to end — pick, pack, parcel, carrier status, proof of delivery — in one screen.

Which statuses and documents are available is set by the carrier contract behind DeliveryMatch: not every carrier supplies a signature or a delivery photo, and proof of delivery on a pallet shipment differs from a parcel. We confirm per carrier what you will actually receive before go-live.

How we roll it out

1. Discovery
We walk through your current DeliveryMatch setup and agree which objects are in scope and which system is leading per object.
2. Connection
The technical connection is established on a test environment first, so you can see real data moving before anything touches your live operation.
3. Mapping and testing
Fields, codes and exceptions are mapped and tested with your own orders — including the ones that normally go wrong.
4. Go live
We go live with your team on the floor, monitor the first days closely and hand over a connection your people can read themselves.

Does your process fit this message set?

This is our standard DeliveryMatch integration. If you need messages that are not in the table, send us your list — we tailor integrations per customer through workflows and will tell you upfront what is standard and what is custom.

Book a technical session Send us your message list

COMPANIES THAT RUN THEIR WAREHOUSE ON BIZBLOQS

More than 200 implementations across wholesale, manufacturing, e-commerce and third-party logistics.

OUR SOLUTIONS

BizBloqs has developed a unique platform which can be configured to create many solutions for every logistic challenge we have encountered.

Every one of these routes runs on the same platform and connects to DeliveryMatch — so whichever route fits you today, the integration does not have to be rebuilt when you move to the next one.

SME

Get off paper. Get in control.

Small and medium businesses running one warehouse, a growing order volume and a team that is doing too much by hand.

Real-time stock accuracy instead of period-end guesswork
Picking errors drop because the system directs every movement
New warehouse staff become productive in days, not weeks

Explore this solution SME+

Multi-channel, multi-warehouse, still fast to change.

Scaling mid-market businesses selling across several channels, holding stock in more than one place, and outgrowing a single-warehouse setup.

One truthful stock position across every warehouse and channel
Orders allocated automatically by rules you control
Oversell and stock-out incidents drop sharply

Explore this solution Enterprise

Multi-entity, deeply integrated, fully auditable.

Larger and multi-entity organisations with complex handling requirements, established ERP landscapes and formal governance obligations.

Complex handling requirements met without custom development
ERP, BI and trading-partner integration through one toolkit
Intercompany flows managed as a first-class process

Explore this solution

Integration FAQ

Does rate shopping slow down packing?

No. The call happens while the packer closes the box; the label prints in the same movement, so the decision costs no floor time.

What if the chosen carrier fails at that moment?

A fallback service is configured per lane. The packer is not asked to solve a carrier outage at the table.

What happens if the DeliveryMatch connection drops?

Messages are queued and replayed. Warehouse work continues in BizBloqs during an outage; the queue drains once the connection is restored, and failed messages stay visible instead of disappearing silently.

Can we change the standard message set?

The table above is our standard integration with DeliveryMatch. Extra messages, different field mappings or customer-specific rules are handled through workflows in BizBloqs — we tell you upfront what is standard and what is custom work.

How long does connecting DeliveryMatch take?

The connection itself is a matter of days. The realistic timeline is set by mapping and testing, and by how clean your product data and process agreements already are.

BEFORE YOU DECIDE

Check the fit from another angle

IndustriesHow your operating model changes the setup.VerticalsSector-specific requirements, from food to spare parts.ROI calculatorPut your own volumes in and see what the current way of working costs.What is a WMS?Where the ERP stops and warehouse management starts.

Hear directly from our customers

Why take our word for it? We let our customers convince you instead. BizBloqs customers are happy with their solutions and don’t hesitate to share their positive experiences. Our ability to turn any challenge into an efficient solution never fails to impress!

Caressi

BizBloqs was one of the first to provide a WMS with scanning capabilities and we started a journey together. Our operations have gotten a lot more complex, advanced and especially bigger over the past 5 years and we have simply grown together.

Nick Bisselink, Financial/Operational Director

Lantaarn

When we had extensive logistic requirements beyond the capabilities of our financial solution, BizBloqs shared its expertise to transform Lantaarn’s entire warehouse experience together

Lantaarn Publishers

Fairplant

We needed a better, more transparent and practical system for our incoming and outgoing product flow. A direct overview in our stock and all our logistics movements was really a must. BizBloqs helped us from the start!

Rik Klein - Sales manager

Neeltje Jans

In addition to a scan procedure with EDI integration, BizBloqs has set up an entire production system for us. Production planning can provide direct instructions and as soon as they are ready, it all arrives in the OMS. This gives us a larger production capacity and a drastic reduction of the picking mistakes in dispatching.

Reinier Schot, Head of Production

Caressi

Nick Bisselink, Financial/Operational Director

Lantaarn

When we had extensive logistic requirements beyond the capabilities of our financial solution, BizBloqs shared its expertise to transform Lantaarn’s entire warehouse experience together

Lantaarn Publishers

Fairplant

Rik Klein - Sales manager

Neeltje Jans

Reinier Schot, Head of Production

Caressi

Nick Bisselink, Financial/Operational Director

Lantaarn

When we had extensive logistic requirements beyond the capabilities of our financial solution, BizBloqs shared its expertise to transform Lantaarn’s entire warehouse experience together

Lantaarn Publishers