Skip to content

Sales and warehouse: one flow for every order

An order from any channel follows the same path: reservation, warehouse allocation, picking, packing, shipment and goods issue. When the rules give no answer, the task goes to the "needs a decision" queue, not "somewhere".

From order to shipment

  • Orders and "To do today"

    Order list and details with an audit log, manual orders, hold and cancellation, and a screen gathering what needs attention today.

  • Order state machine

    Allowed transitions are defined in one place, each recorded in an immutable audit log. Order import is idempotent, so the same order is never created twice.

  • Picking and packing

    Picking orders with a route through warehouse locations, packing with scans, parcels, shipment with a goods issue document and cost of goods sold, and partial shipment.

  • Returns

    Receiving a return into the warehouse as usable or damaged, completing or rejecting it.

Reservations, channel pools and allocation

  • Reservations without overselling

    Reservations are atomic, so parallel orders for the last item will not sell it twice. Unpaid orders have a reservation expiry time.

  • Channel pools

    For each channel you can set how much stock you allocate to it: a percentage, a fixed quantity or everything, with a safety buffer.

  • Warehouse allocation rules

    The first matching rule, by priority, selects the warehouse. If an item is out of stock, the selected mode applies: wait for delivery, partial shipment, hold or ask.

  • Sales bundles

    Selling a bundle is broken down into its components at reservation and goods issue.

  • Proposed MM stock transfers

    When a channel's pool in one warehouse falls below the threshold, Piotr proposes a transfer. Nothing moves without approval.

  • Reservation mismatch alert

    A manual RW or MM document issued after a reservation can throw stock levels out of sync. The "To do today" screen shows this.

Price lists, customer groups and limits

  • Price lists and quantity thresholds

    The price is determined in this order: counterparty price list, customer group, channel, and finally the product price with the group discount. Quantity thresholds lower the price for larger orders.

  • Credit limits and payment terms

    Exceeding the limit holds the order at confirmation. Releasing it with the limit exceeded requires finance permission.

Platform connections

The customer enters their own connection keys, and Zaksio provides the integration code. The first sync run overwrites stock levels on the platform with those calculated by Zaksio, so it is manual and preceded by a connection check. The "Connection" and "Synchronisation" tabs in the channel guide you through these steps.

  • Beta

    Allegro

    OAuth, orders, listings, stock levels, parcel number and optionally prices. Returns from the platform only notify the team.

  • Beta

    WooCommerce

    Orders, listings with variants, stock levels, prices and parcel number as a note. No returns.

  • Beta

    Shopify

    Orders, listings, stock levels, prices and fulfilment with parcel number (GraphQL API). No returns.

  • Beta

    PrestaShop

    Orders, combinations, stock levels and parcel number. No prices or returns.

  • Import from file

    Import from a CSV file (including Vinted)

    Orders and listings from a file, with an error preview. Vinted has no public API for sellers, so there is no stock or parcel synchronisation.

  • Customer API and webhooks

    Products, stock levels, counterparties and invoices via the public API v1, and signed webhooks for your system.

  • Beta

    Amazon.pl

    SP-API: FBM orders, listings by SKU, stock levels, prices and shipment confirmation. Requires Amazon's approval of developer roles.

  • Beta

    Erli

    Orders, listings, stock levels, prices and parcel number. No product creation.

  • Beta

    Empik Place

    Mirakl platform: orders, listings, stock levels and shipment. Without prices and without order acceptance, and access requires an agreement with Empik Place.

  • Beta

    Zalando

    Orders, stock levels, prices and parcel by EAN. No listings or returns, only for partners with a contract and access to the partner portal.

  • Beta

    Temu and AliExpress

    Orders, listings, stock levels and shipping (Temu without prices). Requires an approved app and a seller account.

  • Beta

    Google (Merchant Center) and Facebook/Instagram (catalogue)

    Listing-only channels: listings, stock levels and prices, without orders. Products must already exist on the platform.

Beta: Integrations marked Beta are being rolled out together with our first customers.

Manage smarter. Grow faster.

You can start with one company and a few invoices.

  • Free, no card required
  • Free Start plan with no time limit

Talk to us