Skip to content

Bijection for Retail & E-commerce

One order record. Not four screens.

Storefront, warehouse, ERP and carrier combined into one order that names where each part came from.

Get started

An order is paid in Shopify, allocated in the ERP, picked in the warehouse and handed to a carrier. When a customer asks where it is, support checks four screens, and when two disagree nobody knows which is right.

Bijection combines them into one order record that names where each part came from, and shows both sides, dated, when systems disagree. Forcing an allocation or splitting a shipment becomes a reviewed action, not a direct edit.

  • Stuck orders

    Starts: An order is paid but still unallocated a day later

    1. Add it to the exception queue with the reason.
    2. Someone forces the allocation or cancels the order.
    3. The action is written to the ERP and recorded.

  • Returns

    Starts: A customer starts a return

    1. Check the order, delivery date and return window.
    2. Refund once the warehouse confirms receipt.
    3. Goodwill above your limit waits for approval.

  • Repricing

    Starts: A merchandiser proposes new prices for a range

    1. Preview margin and the listings affected on a branch.
    2. A second person approves.
    3. The new prices are written to Shopify.

  • Stock mismatches

    Starts: The warehouse and the ERP disagree on stock

    1. Show both counts, dated.
    2. Someone decides which count is right.
    3. The correction is written to the ERP.

  • Split shipments

    Starts: Part of an order is out of stock

    1. Preview shipping what is available now.
    2. Tell the customer what arrives when.
    3. The split is recorded on the order.

  • Carrier delays

    Starts: A carrier reports a delay

    1. Find the orders affected.
    2. Tell each customer the new date.
    3. Shipping refunds past your delay threshold need approval.