Does it handle catch weight?

The ordered quantity is captured exactly as sent — 6 salmon sides, not a guessed weight — so the catch-weight reconciliation your ERP already performs starts from clean data instead of a retyped number. ManualOut does not replace that reconciliation; it stops feeding it errors.

Our customers specify cuts in free text. Does that survive?

"Skin on, pin-boned, 2-3kg" is matched to the product code that means exactly that. The original message also stays attached to the order, so the spec is still readable at the bench.

What about lines that depend on what landed?

"Two boxes hake, whatever's landed" cannot be priced until you know. ManualOut flags it rather than inventing a price, and the rest of the order proceeds.

How fast is it? We are working against shelf life.

Orders are read as they arrive, not batched. An order sent at 6am is extracted at 6am, so the desk is triaging exceptions rather than typing the easy ones while the fish ages.

Seafood & fish

Your customer orders 6 salmon sides. You invoice by the kilo.

Seafood is ordered by piece and sold by weight. It lands when the boat lands and has days to sell. ManualOut reads the order and gets it into your ERP while the fish is still worth money.

The daily reality

What the order desk is actually dealing with

Catch weight breaks normal order entry

The customer orders 6 salmon sides. You invoice by actual weight. That is catch weight — ordering, picking and invoicing are three different numbers, and the desk holds them together by hand.

You cannot sell what the boat did not bring

The order book gets written against product that may not exist by the time anyone reads it.

A day lost is a real share of shelf life

When product sells in days, a day spent in a typing queue costs you money. Fish does not wait for the desk to catch up.

The spec is precise. The message is not.

"Skin on, pin-boned, 2-3kg" arrives as a WhatsApp message. Your system has a code for exactly that, and someone has to go and find it.

Where ManualOut fits

What changes once orders read themselves

Catch weight handled properly

The quantity is captured exactly as the customer sent it, so your ERP's weight reconciliation starts from clean data instead of a retyped guess.

Read on arrival, not in a batch

Orders are extracted as they land. The desk deals with the problems instead of typing the easy ones.

Stock checked before it reaches the ERP

If the landing did not cover the order, that shows up during processing — not at the pick face.

The spec stays with the order

Cut specs and delivery notes stay attached, instead of living in a chat thread nobody can find later.

In the product

A seafood & fish order, read and checked

On the left is the message, as the customer sent it. On the right is what ManualOut made of it — and what it flagged for a person.

ManualOutPO #12058Need attention

Source · WhatsApp06:18

Tideway Fish Co.

Morning — for tomorrow: 6 salmon sides, skin on, pin-boned, 2-3kg 4 x cod loin 200g portions 2 boxes hake, whatever's landed 10kg mussels 3 x seabass whole, 400-600g Same as last week otherwise

The original message stays attached to the order — permanently.

Extracted itemsCordell · QUAYSIDE

Product	Unit	Qty	Line
Salmon Side — skin on, pin-boned, 2-3kgCatch weight — invoiced on actual kg at pick	PCE	6	$255.00
Cod Loin — 200g portion	PCE	4	$27.20
Mussels — rope grown	KG	10	$49.00
Seabass — whole, 400-600gCatch weight	PCE	3	$33.60
Hake — grade not stated"whatever's landed" — needs today's landing to price	BOX	2	—

Order value: $364.80
Minimum: $250.00
Status: Minimum met

Ordered by piece, invoiced by kilo. The catch-weight lines are captured as sent, so your ERP reconciles from clean data rather than a retyped guess — and the one line that depends on the landing is flagged, not guessed.

ERP sync summaryIn ERP

ERP order no.: SO-4471203
Synced by: Automatic
Synced at: 14 May 2026, 10:17 PM
Confidence: 94%

Order received
AI parsing completed
Validation completed
Inventory checked
Synced to ERP
Order confirmed

How orders arrive

The channel mix in this trade

Email leads, but a third arrives by message — early, fast, and against the landing.

Email42%
WhatsApp32%
Voice18%
File upload8%

Illustrative — the typical shape of an order book in this trade, not measured data. Your own mix appears in the dashboard once orders start flowing.

Questions

What buyers in this trade ask

Does it handle catch weight?: The ordered quantity is captured exactly as sent — 6 salmon sides, not a guessed weight — so the catch-weight reconciliation your ERP already performs starts from clean data instead of a retyped number. ManualOut does not replace that reconciliation; it stops feeding it errors.
Our customers specify cuts in free text. Does that survive?: "Skin on, pin-boned, 2-3kg" is matched to the product code that means exactly that. The original message also stays attached to the order, so the spec is still readable at the bench.
What about lines that depend on what landed?: "Two boxes hake, whatever's landed" cannot be priced until you know. ManualOut flags it rather than inventing a price, and the rest of the order proceeds.
How fast is it? We are working against shelf life.: Orders are read as they arrive, not batched. An order sent at 6am is extracted at 6am, so the desk is triaging exceptions rather than typing the easy ones while the fish ages.

Worth a few minutes

Why B2B orders still arrive as messages

Every distributor has tried to move customers onto a portal. Most have quietly given up. Here is why that keeps happening, and what to do instead.

6 min read

See it run on one of your own orders

Send us a real order — the messiest one you can find. We will run it live and show you what happens when it works, and when it does not.

Book a demo Talk to sales