Receive against the business requirement
Bring purchase order context into receiving. Verify the incoming items and quantities, record discrepancies and direct stock into the warehouse.
Book a DemoBring warehouse execution and business context together. Start with SAP Business One and everyday scanning and labeling workflows, Use label templates and design tools, with partial API support for receiving purchase order and container information. More equipment, application and communication connections are planned.
Launch focus
Warehouse executionKeep the commercial context connected while giving warehouse teams tools built for the work on the floor.
Bring purchase order context into receiving. Verify the incoming items and quantities, record discrepancies and direct stock into the warehouse.
Follow stock by zone, location and handling unit while keeping it connected to ERP inventory and document references.
Connect the outbound requirement with pick proposals, picking, packing and the final dispatch handoff.


Renkei can track batch and serial numbers even when the ERP item is not batch- or serial-managed. That warehouse-level detail stays in Renkei rather than requiring the same tracking settings in ERP.
Explore the launch focus, device workflows and planned connections across the Renkei platform.
Connect warehouse execution with ERP inventory and purchasing and sales document context.
Use barcode scanning to identify items, locations and handling units during warehouse tasks.
Create and adjust label templates with an easy-to-use design facility, then preview and print labels for items, cartons and pallets.
Extend stock and handling unit identification to RFID equipment as supported integrations are developed.
Connect weighing equipment to warehouse workflows as dedicated device integrations are built.
Send operational updates and notifications. Conversational warehouse queries form part of the future direction.
Extend warehouse information into external operational systems and customer or supplier applications.
Receive purchase order and container information through available APIs. Coverage is currently partial; confirm the required data and workflow during integration scoping.
Launch focus: the primary business-system connection.
Device workflows: scanning and labeling support; hardware compatibility depends on the device and setup.
Partially available: APIs to receive PO and container information, with limited current coverage.
Planned: roadmap direction, without a committed release date.
Connect physical identification to the warehouse task, rather than treating every device as a standalone tool.
An item barcode identifies the stock. A location barcode verifies where work takes place. An HU or SSCC identifies the carton or pallet being handled.
Use an easy-to-use label template and design facility to create and adjust labels for items and handling units, including cartons and pallets. Preview the result before printing.
Confirm scanner behavior, barcode formats, printer models and label sizes against the intended workflow. RFID and weighing equipment remain separate planned integrations.
Future integrations should carry useful warehouse information to the people and systems that need it.
Email and WhatsApp notifications could bring receipt discrepancies, task exceptions and dispatch updates to the right people.
Future conversational queries could help teams ask where stock is held, what work is pending or which shipments are ready.
Partial APIs already support receiving purchase order and container information. Broader data exchange with external business workflows and additional ERP systems is planned.
Agree what needs to move between systems and how the operational handoff should work.
Define the items, quantities, identifiers and business documents needed by the warehouse workflow.
Agree which system owns each record and when information should be exchanged or confirmed.
Define how discrepancies and unsuccessful exchanges are surfaced and followed up.
Confirm device compatibility, application access and the requirements of the selected connection.
Explore ERP connections, available APIs and device workflows. Using another ERP? Bring us your requirements.
Contact us with the name of your ERP and the warehouse workflows you want to connect. SAP Business One is the current integration focus, and we can evaluate your ERP’s available APIs or data exchange options. We will review the information that needs to move between systems and agree a feasible integration scope with you.
Talk to us about your ERPRenkei connects warehouse execution with SAP Business One inventory and business document context. This brings the purchasing or outbound requirement into warehouse workflows while Renkei manages locations, handling units and the work on the floor. The data, direction and timing of exchanges are defined during implementation.
Partial APIs are available to receive purchase order and container information. Share the data and workflow you need to connect so we can review the current coverage and any additional integration work. Broader API coverage remains planned.
Yes. Renkei supports all barcode scanners and other handheld devices that run Android. It also supports all label printers that use ZPL (Zebra Programming Language), so you can use your existing Android devices and ZPL-compatible printers for warehouse workflows.
Yes. Renkei includes an easy-to-use label template and design facility for items, cartons and pallets. You can create or adjust templates, preview the label and print it as part of warehouse workflows.
RFID, scales, weighbridges, email and WhatsApp connections are planned. If one is important to your workflow, contact us to discuss the requirement and evaluate the integration scope. Availability and delivery plans need to be confirmed for that requirement.
Explore the SAP Business One connection or discuss the equipment and applications your operation depends on.