← Our Partners
BizBloqsSAP Business One

BizBloqs × SAP Business One

SAP DISCIPLINE, WAREHOUSE SPEED

SAP Business One gives mid-market companies real SAP discipline: documents, numbering, audit trail, journal entries. What it does not give you is a shop floor that keeps up with it.

BizBloqs connects through the SAP Service Layer and posts everything back as proper SAP documents — goods receipt PO, delivery, inventory counting — so the warehouse gets barcode speed without your auditor losing a single trace.

Explore SAP Business One

Visit SAP Business One

IS THIS YOU?

Who this SAP Business One integration is for

SAP Business One records every movement perfectly — after somebody types it in. The gap between the pallet moving and the document existing is where your stock accuracy goes.

  • You run SAP Business One and the warehouse is the part that still runs on paper and memory.
  • Bin location management in SAP is either switched off or ignored in practice.
  • You need warehouse speed without losing the SAP audit trail your auditor relies on.

WHAT IS SAP BUSINESS ONE?

ENTERPRISE ERP, MID-MARKET FOOTPRINT

SAP Business One is SAP's ERP for small and mid-sized companies: finance, purchasing, sales, production and stock in a single database, on HANA or SQL Server, on-premise or hosted.

It is document-driven by design, which is its strength in the office and its limitation on the floor: every physical action still has to become a document, and typing those documents after the fact is where accuracy and speed are lost.

EVERY SCAN BECOMES A REAL SAP DOCUMENT

BizBloqs never writes into SAP tables. Receipts, deliveries, counts and corrections are posted through the Service Layer as the SAP document they should be, so SAP validates them, numbers them and creates its own journal entries.

The result is an operation where scanning replaces typing, while the SAP audit trail is not just preserved but more complete than it was — because it now reflects the moment the goods actually moved.

WHAT CHANGES ONCE SAP BUSINESS ONE AND BIZBLOQS ARE CONNECTED

The connection is a data agreement, not a development project. Orders, receipts, stock corrections and shipping confirmations move between SAP Business One and BizBloqs as they happen.

Documents posted through the SAP Service Layer

Every warehouse action lands in SAP as the document it should be — goods receipt PO, delivery, inventory counting, inventory posting — created by SAP itself, with SAP numbering and SAP journal entries behind it.

Scanned receiving against the purchase order

The open purchase order is on the handheld at the dock. Quantities and batches are scanned on arrival, discrepancies are flagged before the driver leaves, and the receipt is in SAP before the pallet reaches its location.

Pick, pack and ship with barcode verification

Picking runs on scanning instead of memory: right item, right batch, right quantity, verified per line. The delivery document in SAP then matches what physically went out, which is what makes the invoice defensible.

Bin, batch and serial control on the floor

Locations, batches, serial numbers and expiry dates are managed operationally in BizBloqs and reported back to SAP, so recalls and traceability questions are answered from scan data rather than reconstructed.

Counting without freezing the operation

Cycle counts run alongside normal work and post as inventory counting documents. The annual stock take stops being an event that costs you a weekend of shipping.

HANA or SQL, on-premise or hosted

The Service Layer is present on both HANA and SQL Server, so the integration is the same whichever platform and hosting model you run.

This is what your SAP Business One 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.

ERP integration

How the SAP Business One integration works

SAP Business One is the SAP ERP for small and mid-market companies. BizBloqs connects to it through the Service Layer, the documented OData interface that SAP ships with both the HANA and the SQL Server variant, so the warehouse works against the live company database rather than an export.

SAP Business One — Service Layer / DI API

OData Service Layer (HANA or SQL) with DI API as fallback, per company database

A dedicated service user is created in your SAP Business One environment and BizBloqs authenticates against the Service Layer with it. Documents are read and posted as proper SAP objects — goods receipt PO, delivery, inventory counting, inventory posting — so the audit trail inside SAP stays intact and journal entries are created by SAP itself. Where a document type is not exposed by the Service Layer in your version, the DI API is used for that object. The connection is bound to a company database; a customer with several company databases gets a connection per database.

What you need

  • SAP Business One 9.x or newer with the Service Layer reachable (HANA or SQL Server)
  • A licensed service user with rights on the relevant company database
  • Outbound HTTPS from the SAP environment to BizBloqs, or a published endpoint if SAP is hosted
  • Agreement on warehouse codes and bin location management inside SAP

Which messages are exchanged

This is the standard interface between an ERP and a WMS, exchanged with SAP Business One as the events happen. Empty cells mean that direction is not part of the standard integration.

SAP Business OneBizBloqs WMS
Articles / itemscore
Into BizBloqsItem master, barcodes, units, weights
Purchase orderscore
Into BizBloqsOpen purchase orders
Out of BizBloqsGoods receipts
Purchase order returnscore
Into BizBloqsReturn-to-supplier orders
Out of BizBloqsReturn deliveries
Sales orderscore
Into BizBloqsOpen sales orders
Out of BizBloqsDeliveries / shipment confirmations
Sales order returnscore
Into BizBloqsCustomer return orders
Out of BizBloqsReturn receipts
Webshop sales ordersoptional
Out of BizBloqsSales orders created outside the ERP
Purchase orders (WMS-initiated)optional
Out of BizBloqsPurchase orders raised in the warehouse
Production ordersoptional
Into BizBloqsOpen production orders
Out of BizBloqsProcessed / completed production
Production time registrationoptional
Out of BizBloqsHours booked per production order
Assembly ordersoptional
Into BizBloqsOpen assembly / kitting orders
Out of BizBloqsProcessed / completed assemblies
Assembly time registrationoptional
Out of BizBloqsHours booked per assembly order
Stock countscore
Out of BizBloqsCycle and annual count results
Stock correctionscore
Out of BizBloqsAdjustments with reason codes

Rows marked optional depend on the modules in your SAP Business One licence and on how your administration is set up. Production, assembly and their time registration require the matching modules.

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.

How we roll it out

  1. 1. Discovery

    We walk through your SAP Business One administration and agree which objects are in scope and which system is leading per object.

  2. 2. Connection

    The technical connection to SAP Business One is set up and validated against a test administration. Access is scoped to the objects in the agreed message set.

  3. 3. Mapping

    Item codes, units, warehouses, locations and reason codes are mapped. Deviations between the ERP and the physical warehouse surface here, not on go-live day.

  4. 4. Test round

    We run a full cycle on a test administration: purchase order in, receipt back, sales order in, delivery back, count and correction. Every message is checked in both systems.

  5. 5. Go-live

    Cut over on the live administration with monitored message queues. Failed messages are visible and can be replayed — nothing disappears silently.

Does your process fit this message set?

This is our standard SAP Business One 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

Does BizBloqs replace SAP bin location management?

It takes over the operational side of it. SAP keeps the warehouse and the financial stock position; BizBloqs runs the locations, the scanning and the pick logic, and posts the resulting documents back. Whether SAP bin locations stay switched on is a mapping decision we make during discovery.

HANA or SQL Server — does it matter?

No. The Service Layer is present on both, and the message set is identical. The database platform only affects performance tuning on the SAP side.

Do you write directly into SAP tables?

Never. Everything is posted as a normal SAP document through the Service Layer or DI API, so SAP validates it, numbers it and creates its own journal entries.

Is stock in SAP Business One updated in real time?

Stock in the ERP is updated on every confirmed warehouse action — receipt, delivery, count, correction. The operational truth lives in the WMS, where stock is tracked per location, batch and serial; SAP Business One holds the financial and administrative position.

Which system is leading for item master data?

SAP Business One. Items, barcodes, units and weights are created and maintained in the ERP and downloaded into BizBloqs. Warehouse-specific attributes, such as pick location or storage class, are maintained in BizBloqs.

What happens if the connection drops?

Messages are queued and replayed. Warehouse work continues in BizBloqs during an ERP or network 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?

Yes. The table above is our standard integration. 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 a SAP Business One implementation take?

The connection itself is a matter of days. The realistic timeline is set by mapping and testing, and by how clean your item master and location structure already are.

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