BUSINESS CASE FOR SAGA COMMERCE

Example case: AI agents for B2B ordering

03 Proposal

The buyer’s agent, and the merchant’s 4.

Every buyer gets an agent that keeps their company’s rules. Every merchant gets 4 agents, each with 1 job. They meet on Saga, and an order goes through only when both sides’ rules agree.

Who acts, and for whom

Follow the water pump for the Golf in bay 2 through them. An agent for the buyer, 4 for the merchant, 1 job each, and the people they hand over to.

  1. Setup agentTurns the catalogue and past orders into rules and thresholdsFor the merchant adminA person approves every change it suggests
  2. Ordering agentTalks to the buyer and decides under the merchant’s rulesFor the merchantFrom the buyer by voice, WhatsApp or email. The buyer’s agent checks the buyer company’s rules and asks the approver. Stops go to a sales rep
  3. Fulfilment agentHolds stock, books the van, writes the orderFor the merchantReads live stock and contract prices in the ERP
  4. Review agentSums up the month and suggests changesFor the merchant adminNever touches a live order
  • Merchant adminThe only one who changes the merchant’s rules
  • BuyerWorkshop lead, a Golf on the lift
  • Buyer’s agentKeeps the buyer’s rules
  • ApproverApproves over the limit
  • Sales repTakes every stop
  • Merchant’s ERPLive stock, contract price
  1. The buyer asks for a part by voice, WhatsApp or email.
  2. Every pick goes to the buyer’s agent, which checks it against the buyer company’s own rules.
  3. A part that fits, inside both sides’ rules, goes to the fulfilment agent as an order.
  4. The fulfilment agent holds stock, books the van and writes the order to the ERP.
  5. Over the limit, the buyer’s agent sends the exact amount to the approver.
  6. Under 70, or on a hard rule like a safety part, the ordering agent stops and hands the case to a sales rep.
  7. Every decision is logged for the review agent.
  8. Each month the review agent suggests a threshold change to the setup agent.
  9. Only the merchant admin applies a change.
  10. The setup agent hands the ordering agent the rules and thresholds it acts under.

The agents in detail

What each is worth and how we test it, what it does, and what it never does.

For the buyer

Buyer’s agent

ValueAssumption

The buyer stays in control without watching every order.

Tested by the workshop visits and the pilot

Does

Keeps the company’s rules: who may order, the spend limit and the approver. Checks every pick against them, asks the approver, and keeps the buyer’s record.

Works for

The buyer’s company, inside the store of the merchant that offers it.

Channels

Voice, WhatsApp, email and the buyer’s account in the webshop.

Never

Spends over the limit without the approver, or takes the order to another merchant.

For the merchant

  • Setup agent

    ValueAssumption

    A merchant fills 1 template instead of running a setup project.

    Tested by the replay and the days from signup to live

    Does

    Replays past orders and suggests each category’s , 85 to start.

    Works for

    The merchant admin, during setup.

    Channels

    Merchant settings.

    Never

    Applies a setting. A person approves each one.

  • Ordering agent

    ValueAssumption

    The buyer gets an answer without waiting for a sales rep.

    Tested by the pilot’s 5 minute pass mark

    Does

    Finds the car, asks 1 question if 2 versions of a part fit, then orders, asks the buyer to confirm, or hands over, and says why.

    Works for

    The merchant, as its voice and chat.

    Channels

    Voice, WhatsApp, email and the webshop.

    Never

    Decides a safety part.

  • Fulfilment agent

    ValueAssumption

    No rekeying, so no typing errors on the way to the ERP.

    Checked in the pilot, against the ERP log

    Does

    Holds stock, books the van and writes the order to the ERP. In the pilot, a sales rep books the van.

    Works for

    The merchant, inside its ERP and van planning.

    Channels

    ERP, sales rep chat, and updates on WhatsApp or email.

    Never

    Changes a price outside the contract.

  • Review agent

    ValueAssumption

    The merchant sees where to trust the agent more, with numbers.

    Tested by the override rate and the monthly threshold review

    Does

    Sums up each category and suggests threshold changes.

    Works for

    The merchant admin, every month.

    Channels

    Merchant settings and a monthly email.

    Never

    Applies a rule change.

Data and decisions

Where things live, and where the language model ends.

Orders, stock and prices stay in the merchant’s ERP. Agents read them live through the connection Saga webshops already use, with SAP and Microsoft Dynamics, and write orders back. Fit data per car comes from a licensed catalogue.

The language model only understands and words the reply. Rules and a score decide.

Where people decide

A merchant can add to this list, never take from it.

Always a person

  • Safety parts: brakes, steering, airbags
  • Weak matches under 70
  • Spend over the buyer’s limit
  • Credit hold
  • Missing contract price
  • No fit data for the part
  • Data older than the merchant allows
  • ERP not reachable
  • Any change to the rules

A wrong decision here costs more than the time an agent saves.

  • BuyerWorkshop lead. Can undo for 10 minutes or until the van leaves, and ask for a person at any step.
  • ApproverWorkshop owner. Signs off the exact amount over the limit.
  • Merchant adminSets and changes the merchant’s rules. Nobody else can.
  • Sales repTakes every case the agents should not decide, overrides logged.

Open to any buyer’s agent

Same rules, plus a check on who it is. The check is built after the pilot.

If a buyer brings an agent from another provider, it first proves who it is and that the buyer’s company allows it. Then it reads the same rules, contract prices and live stock as the buyer’s agent on Saga, and every order lands in the same log and review.

Next: Trust

When the agent may act alone