Skip to content
Zagru

What you promise the customer is what the warehouse is asked to do.

Whatever channel an order comes from, it lands in the same model. Zagru One decides, line by line, which warehouse ships it and when; what the customer was told is what the warehouse does.

The Today screen: records to handle first, their status and the action buttons beside them.
A screen from the productToday: waiting orders and decisions in one list.

What gets easier

What gets easier for your order team

  • One order model for every channel

    API, bulk CSV import or an accepted quote: orders land in the same model, and duplicates are filtered out.

  • Delivery promise and warehouse choice

    Each line gets a warehouse based on stock, safety stock, the warehouse cut-off and transit time; the plan follows that promise.

  • Splitting and backorders

    One order can ship from two warehouses; any shortfall becomes a backorder and is released oldest first when goods arrive.

  • Cancellation rules

    Lines not yet shipped are cancelled and their warehouse allocations released automatically; shipped goods go back through a return.

  • Returns

    A return is recorded, the goods are inspected and, if fit, put back into stock; the return stays linked to the original order.

  • Updates owed to the channel

    Acknowledgements, status, tracking numbers and stock updates are queued, and any that fail to arrive are retried.

With the rest of Zagru One

This solution shares its data with the others on the same platform. No files passed between teams, nothing typed in twice.

  • Warehouse management · WMS

    Receiving, putaway, lot and expiry tracking, picking, packing and counting, with handheld scanners on the floor.

  • Quoting and pricing · CPQ

    Quote requests, configuration, contract-based pricing, approval, versions, acceptance and conversion to orders.

Industries

Where is it used most?

At e-commerce and retail businesses selling through several channels, at 3PL providers fulfilling orders for their customers, and at food businesses distributing from several warehouses.

FAQ

Questions you may have

How do marketplace orders come in?

Orders from marketplaces such as Trendyol, Hepsiburada and n11 come in automatically; the API and bulk CSV import are always open too. During onboarding we plan together which channel to start with.

Who decides the price and the payment?

A price that comes from the channel is kept; otherwise it is calculated from your pricing rules. Payment status comes from the channel; Zagru One does not calculate payments.

How do we see which stage an order is at?

The order status is derived from its lines, so in-between states such as partly shipped or partly delivered show up without anyone updating them by hand.

Let's look at it with your own operation.

Tell us which solution you want to start with; we'll run the demo around your own use case.

  • 30-minute intro with the team that builds the product
  • Demo on your own products and flows
  • No commitment, no sales pressure

Get a demo with your own data

Leave your details and we'll get back to you shortly.

Prefer to tell us more? Open the full form

Request a demo