Skip to content

Supported workflows. Not a published product.

Retail

Prepare orders, replenishment, and site work, with people still deciding.

Aeko prepares order, replenishment, supplier, merchandising, and multi-site operations work. Pricing, credit, and customer promises stay with people.

Retail operations team working across orders, stock, and screens

Buyers

These buyers do not share the same workflow.

Order management, replenishment, merchandising, procurement, multi-site operations, finance, and systems each carry a different piece of the work. Aeko names the roles to bound the first process, not to claim one Agent covers all of them.

  1. 01

    Order management

    Orders arrive in mixed formats and must become an ERP dossier. That is not the merchandising brief.

  2. 02

    Replenishment

    The planner assembles sales, stock, and supplier constraints. That is not order entry.

  3. 03

    Merchandising

    Merchandising prepares assortment and placement. Price stays a separate decision.

  4. 04

    Procurement

    Procurement tracks supplier confirmations and commitments. The Agent prepares. The buyer decides.

  5. 05

    Multi-site operations

    Each site carries its own exceptions. Head office still rebuilds the cross-site view by hand.

  6. 06

    Finance

    Finance reconciles, adjusts, and writes off. That is not an assortment workflow.

  7. 07

    Systems

    IT owns ERP, POS, PIM, mail, and documents. Not the commercial judgment.

Handoffs

Where retail work changes hands.

The stall is not a missing application. It is a dossier rebuilt between tools. ERP, POS, PIM, supplier, spreadsheet, document, and communication systems remain the systems of record.

  1. 01

    ERP

    The ERP holds orders, stock, and postings. It does not hold the rules the team still applies by hand.

  2. 02

    POS

    The POS records site sales. It does not pack the exception.

  3. 03

    PIM

    The PIM describes products. It does not decide substitutions or placement.

  4. 04

    Suppliers

    Confirmations, delays, and gaps arrive outside the ERP and lose an owner.

  5. 05

    Spreadsheets

    Replenishment and reconciliation still live in files nobody reads the same way.

  6. 06

    Documents

    PDFs, delivery notes, and attachments travel beside the system of record.

  7. 07

    Communications

    Customer updates and site chases are still decided in inboxes.

Workflows

One dossier. One boundary. Context that remains.

There is no published retail product. Incoming-order preparation, replenishment, supplier tracking, merchandising, site exceptions, reconciliation, and customer updates follow the same rhythm, without invented results. The same order-intake, replenishment, and exception patterns also cover wholesale and distribution, without a separate sector page.

Incoming-order preparation

Supported workflow. Not a published product.

  1. 01Customer order by email, PDF, or message
  2. 02The Agent prepares an ERP-ready order draft
  3. 03Order management decides matches, price, and credit
  4. 04The approved order is entered in the ERP. Company Brain keeps the mapping.

Replenishment proposals

Supported workflow. Not a published product.

  1. 01Sales, stock, open orders, supplier lead times and minimums
  2. 02The Agent assembles a buying proposal
  3. 03The planner approves unusual quantities
  4. 04The supplier order leaves after agreement. The ERP stays the system of record. Company Brain keeps the constraints.

Supplier-commitment tracking

Supported workflow. Not a published product.

  1. 01Confirmations, delays, gaps, and supplier messages
  2. 02The Agent packs the commitment dossier: evidence, gap, requested action
  3. 03Procurement decides the commitment
  4. 04The approved commitment updates the ERP and Company Brain

Stock and site exception packets

Supported workflow. Not a published product.

  1. 01Shortage, stock gap, site incident, store message
  2. 02The Agent packs evidence, owner, and requested action
  3. 03Site operations decide, including safety-sensitive actions
  4. 04The closed exception updates the ERP, the POS, and Company Brain

Merchandising briefs

Supported workflow. Not a published product.

  1. 01Assortment, PIM, sales, site constraints
  2. 02The Agent prepares a brief: products, placement, exceptions
  3. 03Merchandising decides substitutions and placement
  4. 04The approved brief remains in the PIM and Company Brain

Reconciliation preparation

Supported workflow. Not a published product.

  1. 01Invoices, orders, receipts, postings
  2. 02The Agent prepares the gap and the documents to review
  3. 03Finance decides write-offs and adjustments
  4. 04The approved reconciliation updates finance and Company Brain

Customer-update drafts

Supported workflow. Not a published product.

  1. 01Delay, shortage, proposed substitute, decision already taken
  2. 02The Agent drafts the message
  3. 03The team decides the customer promise before send
  4. 04The approved message leaves in the communication tool. Company Brain keeps the decision.

Company Brain

Company Brain keeps the retail context.

This is not another wiki. It is operating context the Agent reuses: mappings, rules, owners, and corrections already approved. Existing systems stay the systems of record.

  • Product and customer mappings01
  • Approved commercial rules02
  • Supplier lead times and minimums03
  • Site identifiers04
  • Exception owners05
  • Previous corrections06
  • Approval thresholds07

Human boundary

The human decision stays visible.

The Agent prepares the dossier. Sensitive actions stop. The boundary is written, not implied by color.

  • Pricing stays with authorized people.
  • Credit stays with authorized people.
  • Substitutions stay with authorized people.
  • Supplier commitments stay with authorized people.
  • Write-offs stay with authorized people.
  • Customer promises stay with authorized people.
  • Safety-sensitive site actions stay with authorized people.

Workflow review

Bring one incoming-order workflow.

In 30 minutes Aeko maps the input, the output, the exceptions, and the decisions that must stay with your order team.