SelfmerceBeta
Book a call

Selfmerce OperatePilot / Early access

From order to resolution, operations in one flow.

Orders, stock, fulfillment, shipping, support and returns in the same customer and profitability context. Exceptions get ranked, a resolution gets prepared, and it's applied at the right level of control.

Review my operations See how an exception gets resolved

One of three areas in a single system — Studio, Launch and Operate come together.

  1. 01Event
  2. 02Diagnosis
  3. 03Options
  4. 04Risk control
  5. 05Action
  6. 06Verification

Overview

You're selling, and the operational load is growing.

The three come as one system; this area also delivers a clear result on its own, on the same product, brand, customer and operations context.

Who is it for?

  • Teams chasing exceptions across several tools
  • Anyone who wants a daily brief and a prioritised exception queue
  • Teams that want support and returns resolved with the order context attached

Not yet

  • Multi-store distribution; depends on the next qualification round
  • Automating high-value financial actions; those stay approved or human-owned

The agent shown on this page

Operations Conductor

Runs orders, stock, fulfillment, shipping, support and returns on one shared priority and SLA system.

First mode: A0–A2 · Brief and diagnosis automatic; refunds, reroutes and goodwill approved.

Specialist capabilities

  • Daily Brief Agent
  • Order Exception Agent
  • Inventory Risk Agent
  • Fulfillment Recovery Agent
  • Support Resolution Agent
  • Returns Agent

Not separate bots: these are specialist capabilities of the Operations Conductor role, working on one context and one record.

Aha workflow

Resolve a late order without losing the customer.

Click through the steps or play the flow: the sources read, the decision, the output and the approval boundary are visible at every step.

Operate

GOALResolve a late order without losing the customer.

Sample scenario
  1. WORKFLOWException event

    Shipment SLA risk raised

    • Order#1842
    • SLA6 h left
    • PriorityHigh
  2. WORKFLOWException event

    Shipment SLA risk raised

    • Order#1842
    • SLA6 h left
    • PriorityHigh
  3. WORKFLOWException event

    Shipment SLA risk raised

    • Order#1842
    • SLA6 h left
    • PriorityHigh
  4. WORKFLOWException event

    Shipment SLA risk raised

    • Order#1842
    • SLA6 h left
    • PriorityHigh
  5. WORKFLOWException event

    Shipment SLA risk raised

    • Order#1842
    • SLA6 h left
    • PriorityHigh
  6. WORKFLOWException event

    Shipment SLA risk raised

    • Order#1842
    • SLA6 h left
    • PriorityHigh
WORKFLOWException event

Shipment SLA risk raised

  • Order#1842
  • SLA6 h left
  • PriorityHigh
  • Agent
  • Workflow
  • Human gate
  • Verified result

Modules

Which modules does Operations Conductor coordinate?

  • 01

    Operations Brief

    The day's most important exceptions, their commercial impact, owner and next action.

  • 02

    Orders

    Validation, allocation, routing, splits, cancellations and lifecycle exceptions.

  • 03

    Inventory

    Stockout, overstock, availability, transfers and replenishment drafts.

  • 04

    Fulfillment

    Warehouse/3PL tasks, priority, capacity, retries and reassignment.

  • 05

    Shipping

    Manual fulfillment, merchant-entered carrier/tracking data and delay visibility.

  • 06

    Support

    Intent, customer/order context, drafted responses and in-policy resolutions.

  • 07

    Returns

    Eligibility, RMA, exchange, refund and restock coordination.

  • 08

    Reconciliation

    Detecting and recovering differences across payment, inventory, fulfillment and provider state.

Trust boundaries

What does it do automatically, what does it leave as a draft, what comes for approval?

Authority grows per action, not per store; these boundaries describe the first launch scope.

Automatic
Read-only brief, classification, SLA, internal routing, safe retries and reconciliation diagnosis.
Within limits
Read-only checks and code-owned notification/recovery steps.
Approval
Refunds, inventory movement, order reroutes, reships and customer goodwill.
Human-owned
Policy exceptions, unknown financial outcomes and high-value actions.

The full trust and autonomy model

Frequently asked questions

Does Operate issue refunds or reroute on its own?

No. Refunds, inventory movement, cancellations and customer goodwill all come for approval. Fulfillment and tracking remain merchant-entered in the pilot.

Does AI answer the support messages?

The Support Resolution Agent drafts a reply with the customer and order context and proposes an in-policy resolution; what actually reaches the customer goes out as an approved template or with human approval.

What happens to my existing warehouse and carrier integrations?

The pilot does not connect warehouse or carrier APIs. We use configured shipping prices, manual fulfillment and merchant-entered tracking; provider-specific connectors require separate qualification later.

Let's agree the first scope that works

Let's move your operations from an alert list to a decision system.

Share the exceptions that eat the most time today, and we'll pick the first working scope together.

Review my operations See the whole system first