BizBloqs × SAP S/4HANA Cloud

ENTERPRISE SAP, WAREHOUSE EXECUTION

SAP S/4HANA Cloud is the system of record for the whole enterprise — and it is deliberately closed: released APIs only, no database access, no Z-tables.

BizBloqs connects the way SAP intends, through a communication arrangement and released OData services, and gives the floor barcode-driven execution while every movement lands in S/4HANA as a real material document.

Book a demo Visit SAP S/4HANA Cloud

Explore SAP S/4HANA Cloud

Visit SAP S/4HANA Cloud Integration docs

IS THIS YOU?

Who this SAP S/4HANA Cloud integration is for

S/4HANA knows the order, the cost and the plan to the cent. It does not know which pallet the operator actually took, or whether the batch on the truck matches the batch on the delivery.

You run S/4HANA Cloud and the warehouse is still spreadsheets, paper pick lists and trust.
You do not run EWM, or you run it centrally and need faster execution at specific sites.
IT will only approve an integration that stays on released APIs with no custom ABAP.

WHAT IS SAP S/4HANA CLOUD?

ONE IN-MEMORY CORE FOR THE ENTERPRISE

SAP S/4HANA Cloud runs finance, procurement, supply chain, manufacturing and sales on a single in-memory core, delivered as a cloud tenant with a release cycle SAP controls.

That governance is exactly why the warehouse gap hurts: you cannot bolt custom code onto the floor process. What is needed is an execution layer that speaks the released APIs and never touches anything else.

RELEASED APIS, NO CUSTOM ABAP

Your SAP administrator creates a communication system, a communication user and a communication arrangement that whitelists exactly the API scenarios BizBloqs needs. Nothing broader is requested and nothing is written outside them.

Because the connection stays on released APIs, an S/4HANA upgrade stays an upgrade instead of becoming an integration project. Traffic can run point-to-point or over SAP Integration Suite on BTP, whichever your IT landscape prefers.

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 SAP S/4HANA CLOUD AND BIZBLOQS ARE CONNECTED

The connection is a scoped API agreement, not a development project. Materials, purchase orders, sales orders, deliveries and inventory postings move between S/4HANA Cloud and BizBloqs as they happen.

Released OData APIs via a communication arrangement

Everything runs over API scenarios your own SAP administrator whitelists in the communication arrangement, so the scope of the integration is documented inside SAP and revocable from inside SAP.

Goods movements posted as real material documents

A scan on the floor becomes a goods movement in S/4HANA — real material document, real posting date, real valuation — rather than a spreadsheet correction somebody keys in the next morning.

Outbound delivery picking and confirmation

Outbound deliveries are picked and confirmed against the S/4HANA document, so what leaves the dock and what the ERP believes left the dock are the same thing, line for line.

Batch, serial and expiry control on the floor

Batches, serial numbers and expiry dates are managed operationally in BizBloqs and reported back, which turns a recall question into a query instead of a reconstruction exercise.

Physical inventory documents for count corrections

Cycle counting runs alongside normal work and posts physical inventory documents, so accuracy is maintained continuously rather than defended once a year.

Point-to-point or over SAP Integration Suite

Whether the traffic runs point-to-point or through SAP Integration Suite on BTP, the message set is identical — the routing choice belongs to your IT landscape, not to the warehouse.

This is what your SAP S/4HANA Cloud 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

ERP integration

How the SAP S/4HANA Cloud integration works

SAP S/4HANA Cloud is the enterprise SAP ERP, and it is deliberately closed: no database access, no custom tables, everything through released APIs. BizBloqs connects the way SAP intends — a communication arrangement with a technical communication user, against the released OData services for materials, purchase orders, sales orders, deliveries and inventory postings.

SAP S/4HANA Cloud — OData APIs via SAP BTP

Whitelisted OData v2/v4 APIs through a communication arrangement, optionally routed over SAP Integration Suite

Your SAP team creates a communication system, a communication user and a communication arrangement that whitelists exactly the released API scenarios BizBloqs needs — nothing broader. From there the warehouse works against live S/4HANA data: outbound deliveries are picked and confirmed, goods movements are posted as real material documents, and physical inventory documents carry the count corrections. Where volumes or eventing require it, the traffic is routed over SAP Integration Suite on BTP instead of point-to-point, which is usually what enterprise IT prefers because it keeps monitoring, retry and certificate management inside the SAP landscape. Multiple plants and storage locations are supported in one connection; separate S/4HANA tenants get a connection each.

What you need

SAP S/4HANA Cloud (public or private edition) with the relevant released OData APIs available
A communication arrangement and technical communication user created by your SAP administrator
Certificate or OAuth credentials, and BizBloqs allowed through any API management or firewall rules
Agreement on plant, storage location and material master ownership between SAP and BizBloqs
Optional: SAP Integration Suite on BTP when traffic must be routed through middleware

Which messages are exchanged

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

SAP S/4HANA CloudBizBloqs WMS

Into BizBloqs

Out of BizBloqs

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 S/4HANA Cloud 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. Discovery
We walk through your SAP S/4HANA Cloud administration and agree which objects are in scope and which system is leading per object.
2. Connection
The technical connection to SAP S/4HANA Cloud is set up and validated against a test administration. Access is scoped to the objects in the agreed message set.
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. 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. 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 S/4HANA Cloud 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 SAP S/4HANA Cloud — 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

Is this the same connection as SAP Business One?

No. Business One uses the Service Layer of a mid-market product; S/4HANA Cloud uses released OData APIs behind a communication arrangement. Different product, different interface, different governance — which is why it is a separate integration.

Do you need custom ABAP or a Z-table?

No. We stay on released APIs only. That is what keeps the connection upgrade-safe in a cloud tenant where SAP controls the release cycle.

Point-to-point or through SAP Integration Suite?

Both are supported. Point-to-point is faster to stand up; Integration Suite on BTP is usually chosen when your IT wants central monitoring, retry and certificate handling. The message set is identical either way.

Does BizBloqs replace SAP EWM or WM?

For customers who do not run EWM, yes — BizBloqs is the warehouse execution layer. Where EWM is already live, BizBloqs is normally used for specific sites or flows rather than as a replacement, and that scope is decided during discovery.

Is stock in SAP S/4HANA Cloud 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 S/4HANA Cloud holds the financial and administrative position.

Which system is leading for item master data?

SAP S/4HANA Cloud. 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 S/4HANA Cloud 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.

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