BizBloqs × nShift

EVERY CARRIER. ONE PACKING STATION.

Your carrier mix grew one contract at a time, and so did the number of portals your packers have to open. Every extra tab is a place where the wrong address, the wrong service or the wrong weight enters the process.

BizBloqs announces the shipment to nShift at the moment of packing and prints the label in the same movement — the packer scans, the box closes, the parcel is booked.

Book a demo Visit nShift

Explore nShift

Visit nShift

IS THIS YOU?

Who this nShift integration is for

nShift can reach any carrier you have a contract with. It cannot tell you whether the order in front of the packer is complete and correct.

You ship with more than one carrier and packers currently choose between portals.
Your shipping errors are address, weight or service errors rather than picking errors.
You want carrier routing to be a rule you can change, not tribal knowledge.

WHAT IS NSHIFT?

ONE OF EUROPE'S WIDEST CARRIER LIBRARIES

nShift Delivery gives shippers access to hundreds of carriers and services across Europe through a single platform, on the contracts the shipper negotiated themselves.

It solves the carrier side beautifully. It does not know what is physically in the box, which is the half BizBloqs owns.

THE ROUTING DECISION MOVES OFF THE PACKING TABLE

Which service applies to which order — country, weight, value, delivery promise, customer preference — becomes a rule in BizBloqs instead of a judgement call by whoever is packing that afternoon.

Multi-colli shipments, customs paperwork for non-EU destinations and the end-of-day manifest per carrier all run through the same flow.

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 NSHIFT AND BIZBLOQS ARE CONNECTED

The connection is a booking agreement, not a development project. Shipments, labels, tracking codes and manifests move between BizBloqs and nShift as they happen.

Label printed inside the scanning flow

Packing is scan-verified per line; when the last item is confirmed the shipment is announced and the label prints at the station. Nobody switches windows.

Carrier and service chosen by rule

Routing rules live in BizBloqs, so the correct carrier and service follow from the order rather than from who is standing at the table.

Real weights and dimensions per parcel

Weight and dimensions are captured at packing and sent with the announcement, which is what stops the surcharge invoices arriving three weeks later.

Tracking codes back on the order

The track & trace code is written back onto the order and forwarded to the webshop, marketplace or ERP that created it, so the customer notification is triggered by a real parcel.

Multi-colli and customs handled

Shipments that need several boxes get a label per colli with the order kept whole, and non-EU destinations get their customs documents from the same data.

Manifest closed per carrier

End of day closes per carrier with a manifest, so the handover to the driver is a scan instead of a stack of paper.

This is what your nShift 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 nShift integration works

nShift is a delivery management platform with one of the widest carrier libraries in Europe. BizBloqs announces every shipment to nShift from the packing station and receives the label and tracking code back in the same call, so a packer never leaves the scanning flow to open a carrier portal.

nShift Delivery — carrier API

REST API with API key per client, label returned as PDF or ZPL

Your carrier contracts stay in nShift, where they belong. BizBloqs holds the routing rules: which service applies to which order, based on country, weight, value, delivery promise and customer preference. At the moment of packing the shipment is announced, the label prints at the station and the tracking code goes back to the order, the webshop and the ERP. Multi-colli, customs paperwork and end-of-day manifests are part of the same flow.

What you need

An active nShift Delivery account with your own carrier contracts
API credentials issued from your nShift environment
Label printers reachable from the packing stations
Agreed routing rules per country, service and delivery promise

Which messages are exchanged

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

nShiftBizBloqs 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 nShift, 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 nShift: 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
nShift 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
nShift 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 nShift: 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 nShift 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 nShift 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 nShift — 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

Do we keep our own carrier contracts?

Yes. nShift is the delivery layer on top of the contracts you negotiated yourself; BizBloqs never sits between you and your carrier commercially.

Can we pick a carrier per order automatically?

That is the point of the integration. Routing rules live in BizBloqs, so a packer scans and the right service is chosen — instead of a human deciding at the table.

What happens if the nShift 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 nShift. 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 nShift 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