← Our Partners
BizBloqsZineps

BizBloqs × Zineps

SHIP FIRST. WORRY ABOUT THE CARRIER LATER.

A pack line stops for two reasons: something is missing, or somebody has to decide something. Carrier choice is the second kind, and it is entirely avoidable.

With Zineps connected, BizBloqs verifies the order by scan, builds the colli, captures weight, announces the shipment and prints whatever label comes back.

Explore Zineps

Visit Zineps

IS THIS YOU?

Who this Zineps integration is for

Zineps can reach every carrier you use. Whether the parcel contains the right goods is settled before it gets there.

  • You ship with more than one carrier and want one process on the floor.
  • Packers currently retype addresses or weights into a shipping portal.
  • You want returns matched to the original order instead of guessed at goods-in.

WHAT IS ZINEPS?

A SHIPPING PLATFORM FOR MULTI-CARRIER SHIPPERS

Zineps lets Benelux shippers run several carriers under one roof, with one set of shipping rules and one place to look when a parcel goes missing.

BizBloqs supplies the shipment facts underneath: verified contents, real colli, real weight, and the order it belongs to.

ONE SHIPPING PROCESS, WHATEVER IS ON THE BOX

Warehouse staff learn one process. Which carrier ends up on the label is a rule the office maintains, not something the floor has to know.

Returns follow the same path, so a returning parcel is matched to its original order line instead of arriving as an anonymous box.

WHAT CHANGES ONCE ZINEPS AND BIZBLOQS ARE CONNECTED

Shipments, labels, tracking codes and returns move between BizBloqs and Zineps as they happen — no exports, no retyping.

Scan-verified packing before booking

Nothing is announced until the contents are verified by scan, so a booking never gets ahead of the physical goods.

Label and tracking in one call

The label and the tracking code come back in the same call the shipment goes out in; the packer never waits for a second system.

Colli built during packing

Colli are formed during packing with their own weights, which is what makes multi-box shipments behave correctly downstream.

Tracking pushed to the sales channel

Tracking codes are pushed to the webshop or marketplace that created the order, so the customer hears from the channel they bought from.

Returns matched to the order line

An incoming return is linked to the order line it came from, with condition and reason recorded at goods-in.

One process across all carriers

Carrier choice becomes a configuration question rather than a training question for every new warehouse employee.

This is what your Zineps 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.

Carrier integration

How the Zineps integration works

Zineps is a shipping platform used by Dutch and Belgian shippers to run several carriers under one roof. BizBloqs hands the shipment to Zineps at the packing station and prints whatever label comes back, so carrier choice never slows down the pack line.

Zineps — shipping platform API

REST API, shipment announcement and label retrieval per parcel

Packing in BizBloqs is scan-driven: every line is verified, colli are built, weight and dimensions are captured and only then is the shipment announced. Zineps returns the label and the tracking code, which BizBloqs writes back onto the order and forwards to the webshop, marketplace or ERP. Returns and multi-colli shipments follow the same route, so the warehouse has one shipping process regardless of which carrier is on the box.

What you need

  • An active Zineps account with your carrier contracts configured
  • API credentials from your Zineps environment
  • Label printers at the packing stations
  • Agreement on which service is used per destination and delivery promise

Which messages are exchanged

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

ZinepsBizBloqs WMS
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 Zineps, BizBloqs and the system your order came from.

The relay chain

  1. 1. Shipment booked

    When the packer confirms the shipment, BizBloqs announces the parcel to Zineps: 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. 2. Label returned

    Zineps 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. 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. 4. Status updates by webhook

    Zineps 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. 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. 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 Zineps: 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. 1. Discovery

    We walk through your current Zineps setup and agree which objects are in scope and which system is leading per object.

  2. 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. 3. Mapping and testing

    Fields, codes and exceptions are mapped and tested with your own orders — including the ones that normally go wrong.

  4. 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 Zineps 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.

COMPANIES THAT RUN THEIR WAREHOUSE ON BIZBLOQS

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

Caressi — BizBloqs
KTC — BizBloqs
Probo — BizBloqs
Neeltje Jans — BizBloqs
NL Pharma — BizBloqs
iXXXi — BizBloqs
Lantaarn Publishers — BizBloqs
Ahrend — BizBloqs
GD Medical — BizBloqs
STERIS — BizBloqs
ESE International — BizBloqs
Homeij — BizBloqs

Integration FAQ

Where is the carrier chosen — in Zineps or in BizBloqs?

BizBloqs decides which service applies, based on the order and your rules; Zineps executes it against the carrier. That keeps the decision next to the stock and the delivery promise.

Does the tracking code reach our customer automatically?

Yes. The code is written back onto the order and pushed to the channel that created it, so the customer notification comes from your webshop or marketplace as usual.

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

Explore further

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

Caressi logo
Five star rating

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

Lantaarn logo
Five star rating

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

Fairplant logo
Five star rating

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

Neeltje Jans logo
Five star rating

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

transform your business

Ready to take the next step? Reach out and let's explore how BizBloqs can work for you.

Download the app

Google PlayApp Store

Two questions about your own operation

Book a demo