Meet Parcel · Your AI commerce coworker Coming soon

Hire Parcel to chase every
order and every refund

Order status, refunds, returns and shipping exceptions across your store and your carriers, answered in the channel before the customer asks twice.

5Workers in the crew
0Refunds issued without approval

Everything Parcel does

Each area runs on the same engine. Most customers switch one on and add the rest as other teams ask for them.

Order tracking

Every order from checkout through to delivered, with the ones that stopped moving separated from the ones that did not.

Shipping exceptions

Catches the stuck shipment while it is still a courier problem, not yet a support ticket.

Refund handling

Checks the request against policy, assembles the evidence, and prepares the refund for a person to issue.

Returns

Tracks the return from request to restock, and tells you when one has gone quiet in the middle.

Customer answers

Status questions answered in the channel from the live record, not from a screenshot someone pasted.

Exception reporting

The pattern behind the one-offs: which route, which carrier, which SKU keeps producing them.

Parcel doesn't just answer questions about your data. It models it.

The ontology is what separates a coworker from a chatbot. Parcel holds your commerce world as objects it can reason over and act on, not documents it searches.

Objects it models

Order
Line item
Shipment
Refund
Return
Customer
Payment
Carrier event

Actions it can take

Prepare refund
Reship
Escalate to carrier
Answer customer

Each one gated on a named human.

Functions it computes

In-transit age
Exception rate
Refund exposure

Derived live from the systems of record.

A stuck order, end to end

Store and carriers in, one approved resolution out.

01 · Ingest
Store and carriers in

Orders, payments, shipments and messages read into the ontology.
02 · Resolve
One order, one object

Store, payment and carrier records joined into one Order.
03 · Compute
In-transit age

Against that route's normal, not a flat threshold.
04 · Surface
Flagged in the channel

Before the customer opens a ticket.
05 · Act
Resolution prepared

Reship or refund, drafted and held for approval.

A tracking page stops at step 4. Parcel goes all the way to step 5.

What Parcel connects to

Your store, your payments and your carriers, read live, with money movement gated on a person.

Commerce

Shopify

Payments

Stripe

Shipping

Carrier tracking

Support & comms

Email
Slack

Parcel is five workers, not one prompt

Each step of the loop is a separate worker from the Onetab Store, with its own tools and its own guardrail. That's why Parcel can be audited step by step, and why a failure in one stage doesn't silently corrupt the next.

IngestOwns the connections and the refresh.
ResolveOwns identity across systems.
ComputeOwns scoring and derived fields.
SurfaceOwns what reaches the channel.
ActOwns the write, behind approval.

Built for controlled commerce operations

A named owner

Parcel belongs to a person, not a department. That person approves, and their name is on the record.
Approval gates

Every irreversible action pauses and waits. Parcel proposes; a person decides.
Row-level security

Parcel sees what the approver is allowed to see, and no more.
Spend caps and audit

A per-agent budget, and every run stored and replayable for whoever asks.