← Our Partners
BizBloqsTAS TMS

BizBloqs × TAS TMS

TRANSPORT PLANS. THE WAREHOUSE CONFIRMS.

Transport and warehouse are usually two organisations that meet at a loading door and disagree about what should be standing there.

With TAS TMS connected, the planner receives shipments that the warehouse has physically confirmed, and the warehouse loads against the trip the planner released.

Explore TAS TMS

Visit TAS TMS

IS THIS YOU?

Who this TAS TMS integration is for

Your TMS plans trips. Your WMS knows what is ready. Today those two facts meet on the dock, at the worst possible moment.

  • You run TAS TMS and a warehouse that still confirms readiness by phone or list.
  • Trips are planned for goods that are not finished picking.
  • Delivery exceptions arrive as paperwork days after the fact.

WHAT IS TAS TMS?

TRANSPORT MANAGEMENT, NOW UNDER SINARI BENELUX

TAS TMS is a transport management system for carriers and shippers with their own fleet, carried today under the Sinari Benelux brand.

The system and the integration are unchanged; only the name above the door is different, which is worth knowing when you go looking for their website.

NO MORE SHIPMENTS THAT EXIST ONLY ON PAPER

What goes to TAS is what has been picked and confirmed, on the load carriers it is actually standing on.

Trips and stop sequences come back, loading is scanned against them, and delivery results — including refusals and damages — open the right process in the warehouse.

WHAT CHANGES ONCE TAS TMS AND BIZBLOQS ARE CONNECTED

Transport orders, load units, planning and delivery outcomes move between BizBloqs and TAS TMS on the agreed rhythm.

Only confirmed shipments planned

A shipment reaches the planner only once the warehouse has confirmed it, which removes the recurring argument about what is actually ready.

Load carriers as physically built

Load carriers are reported as built — pallet, roll container, colli — so the trip is planned on real space and weight.

Trips and stop sequences back

Trips and stop sequences come back into BizBloqs and drive the loading instruction on the floor.

Scanned loading against the trip

Every unit is scanned onto the trip, so a pallet cannot leave on the wrong vehicle without the system noticing.

Delivery results on the order

Delivery results are written back on the order, including refusals and damages with their reason.

File or API exchange supported

Where your transport organisation works with scheduled file exchange rather than APIs, that route is supported as standard.

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

Transport integration

How the TAS TMS integration works

TAS TMS — now carried under the Sinari Benelux brand — is a transport management system used by carriers and shippers with their own transport operation. BizBloqs feeds it shipments that are physically ready and receives the trip planning back.

TAS TMS (Sinari Benelux) — transport management

File or API exchange of transport orders, load units and delivery status

The warehouse confirms what is picked, on which load carrier and in what quantity; that is what goes to TAS. Planning returns as trips and stop sequences, and loading in BizBloqs is scanned against the trip so nothing leaves on the wrong vehicle. Delivery results, including refusals and damages, come back and open the corresponding return process in the warehouse.

What you need

  • An active TAS TMS / Sinari environment
  • Agreed exchange method (API or scheduled file exchange) and message layout
  • Load carrier and colli definitions agreed between warehouse and transport
  • Cut-off times per depot and per trip

Which messages are exchanged

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

TAS TMSBizBloqs WMS
Transport orderscore
Into BizBloqsPlanned trips, routes and time slots
Out of BizBloqsShipments ready to plan
Load unitscore
Out of BizBloqsPallets, roll containers and colli per shipment
Addresses and time windowscore
Into BizBloqsDelivery windows per stop
Out of BizBloqsDelivery addresses and instructions
Loading sequencecore
Into BizBloqsStop sequence per trip
Out of BizBloqsLoading confirmation per unit
Track & traceoptional
Into BizBloqsTracking link and live ETA per stop
Departure / arrivaloptional
Into BizBloqsETA and arrival confirmation
Out of BizBloqsGate-out confirmation
Proof of deliveryoptional
Into BizBloqsSignature, photo and delivery status
Deviationsoptional
Into BizBloqsRefusals, damages and failed deliveries
Out of BizBloqsReturn receipt in the warehouse
Transport costsoptional
Into BizBloqsRate or cost per trip

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 TAS TMS, BizBloqs and the system your order came from.

The relay chain

  1. 1. Shipment offered for planning

    Once a shipment is physically ready, BizBloqs offers it to TAS TMS with its real load: pallets, roll containers, colli, weights, address and time window. The planner works with what is actually on the floor instead of an estimate.

  2. 2. Trip and stop sequence back

    TAS TMS returns the trip with its stop sequence and time slots. BizBloqs drives loading from that sequence — last stop loaded first — and every load unit is scanned onto the trip, so what leaves the dock matches the plan.

  3. 3. Tracking reference stored

    The trip reference and the customer-facing tracking link or ETA come back from TAS TMS and are stored on the shipment in BizBloqs. From this moment the reference exists in the WMS and can be relayed onwards.

  4. 4. Trip status back

    Departure, arrival, live ETA and deviations per stop come back from TAS TMS as the driver works through the trip, so the warehouse sees progress without calling the cab.

  5. 5. Proof of delivery

    The driver's proof of delivery — signature, photo, timestamp and receiver name — is attached to the shipment. A refusal, damage or failed delivery arrives on the same channel and becomes a return receipt in the warehouse instead of a phone call.

  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 depends on how TAS TMS is set up and on what your drivers register: not every trip produces a signature or a photo, and a customer-facing tracking link is only as good as the ETA behind it. We confirm what you will actually receive before go-live.

How we roll it out

  1. 1. Discovery

    We walk through your current TAS TMS 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 TAS TMS 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

Is TAS TMS the same company as Sinari?

Yes — TAS TMS operates under the Sinari Benelux brand. The system and the integration are unchanged; only the name on the door is different.

Can we exchange by file instead of API?

Yes. Scheduled file exchange is a supported route where that is how your transport organisation already works.

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