SelfmerceBeta
Talk to us

How it works

Set a goal. Let the system carry it to a result.

The agent understands the goal and coordinates; workflows run the reliable steps; the critical decision reaches a human at the right moment. All of it on one commerce context and action ledger.

Watch a sample flow Read the trust model

The working loop

Six steps from a goal to a verified result.

Every step's role is spelled out in words: agent, workflow, human gate, verified result.

  1. 01Human

    Goal

    You describe an outcome: "Have the store ready to sell by Friday." The agent takes a goal, not a command.

  2. 02Agent

    Context

    Product, brand, customer, order, stock and policy truth is read from Core, with the source shown.

  3. 03Agent

    Plan

    The work is broken into steps, and each step gets a role: agent, workflow or approval.

  4. 04Workflow

    Preparation

    Safe, reversible parts become an exact diff or a draft; nothing reaches the outside world unapproved.

  5. 05Human gate

    Human gate

    Anything touching money, price, publishing or the customer comes to you — with impact, risk and a rollback plan.

  6. 06Verified result

    Apply and verify

    The approved plan runs unchanged; the result is re-read from the source system and written to the record.

Sample scenarios

One model; three different jobs across Studio, Launch and Operate.

Click through the steps or play the flow: goal and timeline, active step, evidence and result.

GOALTurn a supplier file and 8 product photos into a channel-ready catalog.

Sample scenario
  1. HUMANSource package

    Supplier file and images uploaded

    • Source file1 xlsx
    • Images8
    • Target channels2
  2. HUMANSource package

    Supplier file and images uploaded

    • Source file1 xlsx
    • Images8
    • Target channels2
  3. HUMANSource package

    Supplier file and images uploaded

    • Source file1 xlsx
    • Images8
    • Target channels2
  4. HUMANSource package

    Supplier file and images uploaded

    • Source file1 xlsx
    • Images8
    • Target channels2
  5. HUMANSource package

    Supplier file and images uploaded

    • Source file1 xlsx
    • Images8
    • Target channels2
  6. HUMANSource package

    Supplier file and images uploaded

    • Source file1 xlsx
    • Images8
    • Target channels2
HUMANSource package

Supplier file and images uploaded

  • Source file1 xlsx
  • Images8
  • Target channels2
  • Agent
  • Workflow
  • Human gate
  • Verified result

Not every automation is an agent. And no agent acts freely.

Agent

Understands the goal, gathers evidence, compares the options and coordinates the modules.

ExampleReduce late deliveries.

Workflow

When an event and a rule line up, it runs the reliable action the same way every time.

ExampleOn fulfillment, create the label and start tracking.

Human gate

Brings the decision to you at every budget, price, publish, refund or policy threshold.

ExampleSend the over-limit reshipment for approval.

The difference isn't one more chatbot: agent, workflow and human decision meet on the same commerce context and action ledger.

The work that's a workflow, not an agent

The LLM doesn't decide at every step.

This work runs as event + rule + typed command. The agent interprets the goal, gathers evidence, produces options, coordinates the workflows and escalates the exception to a human.

  • 01Payment failure classification and permitted retry flows
  • 02Catalog or stock sync
  • 03Order validation and rule-based allocation
  • 04Creating fulfillment tasks
  • 05Shipping labels and tracking event processing
  • 06SLA timers and escalation
  • 07In-policy return eligibility checks
  • 08Outbox / webhook retry and reconciliation
  • 09Sending transactional notifications
  • 10Applying the approved plan unchanged

One shared truth for the whole business

What Studio learns isn't lost in Launch. And it isn't rebuilt in Operate.

Commerce Context
Product, brand, customer and order relationships
Semantic Metrics
Revenue, margin, stock, return and SLA definitions
Workflows & Approvals
Rules, approval thresholds, exact plans
Action Ledger
Proposal, decision, outcome and rollback history

ACTION LEDGER · TODAYSample record

  1. 09:14 Studio48 products normalised
  2. 10:32 LaunchReadiness found 5 blockers
  3. 11:08 HumanCheckout release approved
  4. 11:11 WorkflowTest order completed
  5. 14:42 OperateSLA tracking started on first shipment

One context, one set of limits, one chain of record.

The autonomy ladder

One action, five levels of authority.

How is a single stock risk handled at every level, from A0 observation to A4 coordinated agents?

Autonomy ladder

A0

Sample action · Stock risk and transfer

Stockout risk detected

Estimated cover for Linen Pillow / Pearl is 14 days against a 21-day target. The signal comes from sell-through rate and current stock.

Estimated cover
14 days
Target
21 days
Source
Sell-through + stock
System
Gathers data and shows the anomaly and its context with the source.
Merchant
Verifies the data.
Evidence required
A correct, sourced diagnosis.
Control
Read-only · source shown

Risk classes and promotion gates

Let's agree the first scope that works

Bring us one of your goals; we'll map the flow with your own data.

We'll pick the smallest scope across Studio, Launch or Operate that produces a real result.

Talk to us Meet the agents