Vessel Aurelia omitted Kwai Chung; the container arrives 14 days late. Fourteen days of stock.
- Delivery exception
- 1.00
- Urgency
- 3.67 / 5
- With 60 days of stock
- 2.45 / 5
Reorder point recomputed, customer notice drafted, owner and due clock set.
Sorting and chasing
The tide keeps its hour;the urgent stands clear
The inbox is already the ERP. POSHIM reads each arrival, weighs it, and sees it through.
Inbound stream · measured samples004 decided
Customs at Felixstowe asks for the certificate of origin and MSDS under PO-··31, today
Document requestUrgency 3.00
Account frozen due to audit; remit to our new Singapore account, confidential, today
Payment detail changefraud 0.98
PO-··31: cut HX-40 from 500 to 300, ship date moved to 19 October
Order changeUrgency 2.92
Vessel Aurelia omitted Kwai Chung; container PSMU···4383 arrives 14 days late
Delivery exceptionUrgency 3.67
What it does
Seen in the deep, delivered in the light
Connect a single inbox. Each item the tide brings in is classified, ranked and flagged, then carried through the playbook for its kind.
- Compute, then decide
- Stock, arrivals, contract bands and invoice gaps are computed in code; the model only reads.
- Decide, then do
- Recompute, compare, fetch the document, draft the reply or quote, schedule the chase.
- Retuned every week
- Every corrected decision becomes a sample; thresholds retune each week.
The workspace is open. Create one and the thirteen-day trial begins that day. Below is Supply Chain in Motion, POSHIM's first public piece.
How it works
Four steps, ebb and flow
01Perceive
Email over IMAP or forwarding, WeChat and WhatsApp chat exports; PDF and text attachments reduced to text.
02Decide
Category, stock-out exposure, flags, scores — each decision timed and kept on the record.
03Act
Replies, order changes outside the band and payment-detail changes wait for a click; ledger writes from a sender off the counterparty's domain wait for the owner; the rest completes on its own.
04Learn
Thresholds retune weekly per category and language.
One item, decided
Real model output on fictional messages
Two fictional messages run through the production model; the output is shown unedited.
From this month our receiving account moves to our Macau entity; please pay the new invoice. Sender domain matches the file.
- Payment detail change
- 1.00
- Fraud flag
- 0.78
- Blatant version
- 0.98
Payment held, call-back task prepared, awaiting a click.
Production-model output on paired English and Chinese trade emails, shown as returned. All samples are fictional; no client data is used.
Prices
Fixed scope, fixed price
No set-up fee; the first thirteen days are free. Priced against the hours a clerk spends sorting and chasing by hand, not by the seat. Pay monthly, or yearly and save at least two months; stop at any time.
Preliminary, in US dollars; the price shown is the total charged. Every tier exports to Excel and carries the fraud flag.
Basic
$47a month
or $467 a year
- 1,000 items a month
- 1 inbox
- Category, owner and due clock written back
- Weekly open-exceptions report
- CSV export for Excel
Premium
$199a month
or $1,987 a year
- 10,000 items a month
- 3 inboxes
- Category, owner and due clock written back
- Weekly open-exceptions report
- CSV export for Excel
- Chase list and reply drafts, checked before they are shown
- Order changes inside the contract band confirmed on arrival
- Monthly automatic recalibration
Elite
$797a month
or $7,963 a year
- 100,000 items a month
- 5 inboxes
- Category, owner and due clock written back
- Weekly open-exceptions report
- CSV export for Excel
- Chase list and reply drafts, checked before they are shown
- Order changes inside the contract band confirmed on arrival
- Monthly automatic recalibration
- Up to 11 custom categories, each running a fixed playbook
- A 30-minute calibration call each month
Boundaries
Who it suits, what it will not do
Suits
- Trading companies and sourcing agents of 5–50 people
- Small freight forwarders and customs brokers
- Cross-border e-commerce sellers
- Inboxes that mix English and Chinese
Will not
- Send anything in the client's name
- Take on bespoke projects
- Write the client's software
- Run the client's servers
- Sell the model, or fraud detection, on its own
Connects to
- Email (IMAP or forwarding)
- WeChat / WhatsApp chat exports
- PDF and text attachments filed against the order
- Excel, by CSV: open exceptions and the order ledger
Questions
Before connecting an inbox
What does it actually do for me?
It classifies, ranks and flags, then carries each item through its playbook: recompute, compare, fetch, draft, chase. What arrives is finished work, and drafts awaiting a click.
Which actions wait for me?
An outbound reply, an order change outside the contract band (on Basic, every order change), a change of payment details. POSHIM never makes a payment. When the sender's domain does not match the counterparty on file for the order, its ledger writes — marking an order paid, moving an ETA, writing a new order, an in-band order change — go to the owner instead. Any wording about changing bank details always holds the counterparty's payments, whoever sends it, and a payment advice carrying it never marks an order paid. Anything a flag holds also waits — low confidence, an instruction aimed at the system, a quantity far above the buyer's history, a sign of payment redirection — before a line is written to the ledger. Everything else completes on its own, on the record.
What if a decision is wrong?
Every decision carries a confidence, and the uncertain ones already wait for review. Each correction becomes a sample; thresholds retune weekly, and any decision can be changed at any time, on the record.
Can I keep working in Excel?
Yes. Open exceptions and the order ledger download as CSV and open straight in Excel, Chinese intact — on every tier, and during the trial.
Why is it priced this way?
Against the hours someone on the team spends sorting mail, chasing suppliers and checking documents by hand — not against inbox software. Limits rise with the tier; nothing is charged per item or per seat.
Which model decides?
No single model. The arithmetic — stock-out exposure, contract bands, invoice gaps, air-freight cover — runs in our own pipeline. The judgement layer is a dedicated probabilistic model that returns categories, urgency and risk scores, never text. Drafts are fixed templates filled from the message and the ledger, and the judgement layer reads each back for any figure it cannot source. Change a layer and the workflow on screen stays the same.
Where does my data go?
Only the message and the figures computed for it are sent to the judgement service, and only to be decided. Records stay with POSHIM, exported or deleted on request.
The first piece
Supply Chain in Motion
1/7 · Customers take 40 units a day
d = 40 / day · stock 1,400 · Rop = L×d + Ss = 21×40 + 120 = 960
d = 40 / day · stock 1,400 · Rop = L×d + Ss = 21×40 + 120 = 960
T+0.0s
Chaos switches
All stories are fictional; no client data is used.