Question 1

What is BizBloqs?

Accepted Answer

BizBloqs is a Business-Process-as-a-Service (BPaaS) platform that delivers enterprise-grade Warehouse Management (WMS), Order Management (OMS), and system integrations to SMB and mid-market operators across Europe. Founded in 2015 in 's-Hertogenbosch, Netherlands, BizBloqs serves 200+ active customers across 15 industry verticals and has processed more than 7,000,000 shipments.

Question 2

What is a WMS and does BizBloqs provide one?

Accepted Answer

A Warehouse Management System (WMS) controls day-to-day warehouse operations: receiving, putaway, replenishment, scan-driven picking, packing, shipping, and cycle counting. BizBloqs provides a full cloud WMS as part of its BPaaS platform, with handheld and wearable-device support and real-time inventory at location and lot level.

Question 3

How much does BizBloqs cost?

Accepted Answer

BizBloqs is priced per user and per site rather than by transaction volume, which keeps costs predictable as order volumes grow. Exact pricing depends on the number of users, sites, and modules (WMS, OMS, Integrations). Contact BizBloqs for a quote tailored to your operation.

Question 4

What systems does BizBloqs integrate with?

Accepted Answer

BizBloqs ships pre-built connectors for major ERPs (Exact, SAP, Microsoft Dynamics, NetSuite and others), e-commerce platforms (Shopify, Magento, WooCommerce), marketplaces (Amazon, bol.com), carriers (DHL, PostNL, UPS, DPD, GLS and others), and EDI trading partners. Custom integrations are delivered through the same integration layer.

Question 5

How long does a BizBloqs implementation take?

Accepted Answer

Because BizBloqs is workflow-first and pre-configured rather than custom-built, most SMB and mid-market implementations go live in weeks, not months. Actual timing depends on the number of sites, integrations, and the complexity of existing processes, but a single warehouse with standard connectors typically launches in 4 to 12 weeks.

Question 6

Is BizBloqs suitable for 3PL and multi-client warehouses?

Accepted Answer

Yes. BizBloqs supports third-party logistics (3PL) operators with multi-client inventory segregation, per-client billing rules for storage and handling, and portals or APIs that let each shipper's ERP or OMS talk directly to the 3PL's warehouse.

Question 7

Which industries does BizBloqs serve?

Accepted Answer

BizBloqs serves 15 industry verticals: automotive, MedTech, pharmaceuticals, food & beverages, agriculture, fashion, cosmetics & personal care, luxury goods, home & decoration, technology & electronics, fast-moving consumer goods (FMCG), construction, chemicals, paper & packaging, and technical wholesale.

Question 8

Where is BizBloqs based?

Accepted Answer

BizBloqs Management Solutions B.V. is headquartered at Rietveldenweg 12A, 5222 AR 's-Hertogenbosch, Netherlands. The company was founded in 2015 by Willem ten Asbroek and operates across Europe through its own team and a network of 30+ global system integrator partners.

Question 9

How does BizBloqs differ from SAP EWM, Manhattan, or Descartes?

Accepted Answer

BizBloqs is delivered as BPaaS with a workflow-first configuration model, so customers get enterprise-grade WMS and OMS capability without the multi-year implementation and heavy custom development typical of tier-one suites. Pricing is per user and per site rather than by transaction volume, which is a better fit for SMB and mid-market operations.

Question 10

Does BizBloqs offer a demo?

Accepted Answer

Yes. You can request a live demo or a call with a solutions architect from the Contact page. Demos walk through WMS, OMS, and the specific integrations relevant to your operation.

Question 11

Why does my system say 12 when the shelf has 9?

Accepted Answer

Stock drift happens when movements are recorded after the fact instead of at the moment they occur — on paper, in a spreadsheet, or from memory at the end of a shift. A scan-driven WMS records every receipt, putaway, move, pick and adjustment against a location as it happens, so the record and the shelf stay in step and counts confirm rather than correct.

Question 12

How do we stop overselling stock we do not physically have?

Accepted Answer

Overselling is almost always a timing problem rather than a counting problem: the webshop sees yesterday's stock figure. When the WMS holds live inventory at location level and pushes availability to every sales channel as it changes, the channel sells what exists now, and allocation rules reserve stock the moment an order lands.

Question 13

We still pick on paper. What actually changes with scanning?

Accepted Answer

Scan-guided picking replaces the picker's memory and handwriting with a confirmed system instruction: go to this location, scan this item, confirm this quantity. Wrong item or wrong location is caught at the moment of picking rather than by the customer, and the order status is live for anyone who needs it.

Question 14

Our process breaks every peak season. Why?

Accepted Answer

Processes that depend on experienced people break when you add inexperienced ones, and peak means exactly that. Guided workflows move the knowledge out of individual heads into the system, so a temp who started this morning follows the same confirmed steps as a picker with five years on the floor, and training drops from weeks to hours.

Question 15

How should returns be handled so stock becomes sellable again?

Accepted Answer

Returns need a structured intake — register, inspect, grade, then either restock, repair or write off — with each outcome recorded against the item. Without it, returned goods sit in a corner as unrecorded stock you own but cannot sell. A defined returns workflow puts good stock back into availability the same day it arrives.

Question 16

Can we trace a specific batch, serial or expiry date?

Accepted Answer

Yes. BizBloqs records batch, serial and expiry at receipt and carries them through putaway, picking and dispatch, so a recall becomes a query rather than a physical search of the warehouse. FEFO picking rules issue the shortest-dated stock first, which reduces write-off as a side effect of normal picking.

Question 17

Where do the hours actually go in a working day?

Accepted Answer

In most operations the time is lost in searching, walking, waiting for instructions and correcting mistakes, not in the picking itself. Location-driven routing, task interleaving and confirmed instructions attack all four, which is why throughput per picker rises before any new equipment enters the building.

Question 18

Customer service cannot answer where an order is. How is that fixed?

Accepted Answer

That question is only unanswerable when order status lives in someone's head or in a stack of paper. When picking, packing and dispatch are confirmed in the system, the order carries a live status and a carrier reference, so service answers from the same screen the warehouse works in.

Question 19

Can we not just run the warehouse from our ERP?

Accepted Answer

An ERP is a system of record; a WMS is a system of execution. ERP stock modules track what you own and what it is worth, but they were not built for locations, replenishment, wave picking, scan confirmation or floor-level throughput. Stretching one into the other is where most warehouse projects stall.

Question 20

What is a best-of-breed logistics architecture?

Accepted Answer

It is an architecture where each system does what it is best at and the systems are properly connected: the ERP owns finance and master data, the WMS owns warehouse execution, the OMS orchestrates orders across channels, and a governed integration layer carries the messages between them. It only beats a monolith when the connections are versioned and monitored.

Question 21

Do we have to replace our ERP to get a proper WMS?

Accepted Answer

No. The usual path lifts execution out of the ERP and leaves finance, purchasing and master data exactly where they are. The ERP keeps sending articles, purchase orders and sales orders; the WMS sends back receipts, stock mutations and dispatch confirmations. No rip-and-replace, and no re-implementation of your finance stack.

Question 22

Every integration breaks when a supplier updates their API. How do you handle that?

Accepted Answer

Point-to-point scripts break silently; a governed integration layer does not. BizBloqs connects systems through one integration layer with versioned message definitions, monitoring and retry, so a failed message is visible and replayable instead of discovered a week later by a customer.

Question 23

Which system should own which record?

Accepted Answer

Decide it once, before the build: one owner per record, everyone else subscribes. Typically the ERP owns articles, suppliers and pricing, the WMS owns physical stock and locations, and the OMS owns the order lifecycle. Ambiguity here is the single most common cause of data conflicts after go-live.

Question 24

How do you avoid vendor lock-in?

Accepted Answer

Lock-in comes from custom code that only the vendor understands. BizBloqs is configured workflow-first rather than developed per customer, so process changes are configuration your own team can see, and the integration layer speaks standard messages rather than a proprietary dialect.

Question 25

Can BizBloqs handle multiple warehouses or multi-client 3PL setups?

Accepted Answer

Yes. BizBloqs supports multiple sites with separate stock pools and a consolidated view across them, and for 3PL operators it adds per-client inventory segregation, client-specific workflows and billing rules for storage and handling. Each shipper's ERP or webshop can connect directly through the same integration layer.

Question 26

What does the IT side actually have to deliver in an implementation?

Accepted Answer

Less than most IT teams expect, but it must be specific: clean master data, credentials and endpoints for each connected system, a decision on record ownership per domain, and named owners for each connector. Get those four right and the integration work stops being the critical path.

Question 27

How do we build a business case a board will accept?

Accepted Answer

Build it from your own numbers, not a vendor's averages. The defensible lines are labour hours per order, the cost of mispicks and returns handling, stock capital tied up in safety buffer, write-off from expiry or obsolescence, and revenue lost to SLA penalties. Model those on your volumes and the payback period speaks for itself.

Question 28

Is a WMS only worth it above a certain order volume?

Accepted Answer

The trigger is complexity rather than volume. Multiple channels, batch or expiry control, several locations per article, or seasonal peaks push an operation past what spreadsheets can hold long before order counts look impressive. Plenty of operations under a thousand orders a week need one; some above it do not.

Question 29

Will this just mean hiring fewer people?

Accepted Answer

In practice it usually means the same team handling more volume, not a smaller team. Growth stops requiring proportional hiring, new starters become productive in hours instead of weeks, and experienced staff stop spending their day on corrections — which is where the value shows up in most operations we see.

Question 30

What does BizBloqs cost, and how does it scale?

Accepted Answer

BizBloqs is priced per user and per site rather than per transaction, so a peak month does not reprice the platform and growth stays predictable. Exact pricing depends on users, sites and modules — WMS, OMS and Integrations. Contact us for a quote against your own operation.

Question 31

How long before we see a return?

Accepted Answer

Because BizBloqs is configured rather than custom-built, a single warehouse with standard connectors typically goes live in weeks rather than months, so the benefit period starts inside the same financial year. The heaviest gains — fewer mispicks, less searching, faster onboarding — appear immediately after go-live rather than at the end of a phased rollout.

Question 32

What happens to us if the one person who knows the process leaves?

Accepted Answer

Key-person dependency is a real, priceable risk: a holiday or a resignation becomes an operational incident. When the process is configured in the system as guided steps, the knowledge stays with the company. That is a continuity argument as much as an efficiency one, and boards tend to weigh it accordingly.

Question 33

Our marketplaces and carriers keep tightening their requirements. Does that matter commercially?

Accepted Answer

It matters directly. Cut-off times, label formats and delivery promises are contractual, and missing them costs penalties, suppressed listings or a lost channel. Meeting them reliably is a revenue-protection line in the business case, not an IT detail.

Question 34

How does BizBloqs compare commercially with tier-one WMS suites?

Accepted Answer

Tier-one suites deliver deep capability through long, heavily customised implementations priced for enterprise scale. BizBloqs delivers enterprise-grade WMS and OMS capability as a configured service, priced per user and per site, aimed at operations that need the capability without the multi-year project economics.

Frequently Asked Questions

Common questions

Operational problems

Systems and integration problems

Commercial and organisational problems

Ready to see BizBloqs on your own process?