Solution · Dispatch processes
Recurring shipping orders can be handed over in a structured way. PROWERB agrees required data, references, approvals and updates with your system, while exceptions retain a clear handling process.
Accept products, quantities, recipients and a unique reference from the source system.
Resolve incomplete information and missing approvals before execution.
Send agreed order and shipping information back to the originating system.
Every manual step between order and delivery costs time and produces errors: retyping, forwarding, following up, resolving. Four transaction types keep filling the inboxes.
Atlas & Nexus · PROWERB systems
Atlas gives clients access to products, stock, campaigns and orders. Nexus supports operational processing. We agree the views and handovers needed for your project.
PROWERB Core manages orders, items and stock in one system — RFID-capable, with continuous real-time entries. Start with one recurring ordering channel and describe its standard case: an unambiguous item, available quantity, complete delivery address and agreed approval.
Then use an exceptional order to establish who resolves missing details or a quantity change. File exchange can suit batch call-offs; ongoing individual orders need an agreed handover and feedback route. These rules make the connection a dependable dispatch process.
Order-to-cash: one closed loop
Every step booked in the same ERP — no media break, no handover.
> 2 million shipments a yearover the same recurring processes
The visual orders recurring process steps. The important part is continuous booking without a manual handover.
PROWERB has run Vaillant's order and warehouse logistics for almost two decades: standardized order call-offs from the warehouse, goods receipt and inventory management, shipment tracking, courier commissioning and exception handling — continuous ongoing operations with barely any campaign share.
How orders arrive depends on the customer: Erdinger submits order files via SFTP, for the Bitburger summer campaign winner addresses were imported directly from the campaign app, junited AUTOGLAS orders through the promotional-products shop we operate.
Example: order A-104 for 20 approved kits to a branch. Previously a person re-entered the list and requested dispatch status separately. After integration, the same reference follows validation, dispatch and feedback.
A-104, article, quantity, address and approval enter as structured data.
Check duplicates, stock and required fields; missing details go to the agreed exception contact.
Pick and dispatch the approved order; partial delivery follows agreed rules only.
Return order reference, dispatch status and tracking through the agreed channel; monitor transmission errors.
Direct shop connection, SFTP file exchange, direct import from campaign apps, and the MEP platform with connections to existing online shops, ERP and WMS systems. Email-based ordering channels can also be structurally taken over — they become a standard transaction in the system.
Yes. The Operations Cockpit delivers Power BI live reports, track & trace, inventory development and budget control — available around the clock and integrable into your systems.
Exception cases run through defined workflows to account management: three fixed levels — key account, campaign control, operational fulfillment — instead of changing ownership. Non-receipt, transport deviation and returns each have their own process.
Yes. Capacity can be increased to 200 percent of baseline capacity within 24 hours, and to 400 percent of baseline capacity within 72 hours. The campaign line runs 1 to 15,000 shipments per day, with changeover in under three hours.
State intake channel, typical order volume, approvals and required feedback. An anonymised example helps us agree the standard case, exceptions and project scope.
