E-commerce and orders
Between “paid” and “delivered” dey nine jobs
A shop platform handle di basket and di checkout well well, and den e stop. Everything wey come after payment — di invoice, di stock, di warehouse, di courier, di customer wey wan know where dia parcel dey — na somebody morning work, every morning.
Di bakery wey get webshop
Take small bakery wey start to dey sell celebration cakes online during one quiet winter and now dey take forty orders every week. Di shop collect di money. After dat, somebody go open di invoicing system and type di customer details again, mark di stock of one decorating kit down by one, write personal note about collection, and later dat week remember to ask whether di cake sweet.
None of dem hard. All of dem na Tuesday morning work. And di note about collection na di only part wey need human sentence — di rest na di same nine steps in di same order, forty times every week.
- ⚡Wetin dey start amWebhook
order.paid, 289,00 zł, dem go collect am on Saturday. - 2Address checkedPostal code match wit reference data. E bi free, no need for key.
- 3Invoice raisedFields from di order. Nobody type name or address.
- 4Stock adjustedDecorating kit down one. Idempotency key na di order id.
- 5Collection noteAI step. Two warm sentences inside di customer language, inside di bakery tone.
- ✉Dem don send amE-mail wey carry di invoice attached and short link to di collection details.
- ⏸WaitUntil Saturday 18:00, den ask how e be.
Time wey e take: 4.1 sSteps wey call model: 1
Di usual seven
Wetin people build first
Order to invoice
Paid order in, invoice out, with di address validated on di way through so e no go get rejected later by somebody wey im job na to reject invoices. KSeF-ready where di invoicing system support am.
Shipping notice
When di carrier webhook say e don ship, di customer go get message with short link wey dey count im own redirects — so you go know whether people dey click, without tracker inside anybody browser.
Basket wey person abandon
Idle for forty minutes, wait two hours, send one message, split di subject line two ways, and stop di moment di order land. Di goal end di run; nobody go get reminder to buy wetin dem don already buy.
Stock warnings
Nightly pass over stock levels, weighted by how fast each line dey move, e go produce one message with list instead of forty alerts wey nobody dey read.
Wetin e go return
Return request wey dem classify from wetin di customer talk amsef — e spoil, wrong size, or di customer change mind — and dem route am as e be, plus di label wey dem generate for di two out of di three wey no need human being.
Review requests
Dem send am some days after delivery, no be after dispatch, for di customer own language, and dem no send am to person wey im order get problem. Dat last condition na one branch and e save plenty embarrassment.
Di order na di easy part.
Di first of di month
Di reconciliation na di work wey people talk last but value pass. Di shop talk one thing, di payment provider talk another, di accounting system talk di third, and di difference almost always get explanation — refund wey dem post late, payout wey cross month boundary, or currency conversion wey dem do with small different rate.
Almost always. Di workflow no dey do di sums, wey easy, but e dey do dem every day so dat first of di month go get four items to check instead of four hundred.
Selling abroad
Reference data dey do quiet work here. Country code wey real. Currency wey exist. Postal code wey belong to di city wey dey beside am. Address wey dem normalise to di shape wey di carrier for dat country expect, no be di shape wey your form collect.
Di message wey di customer receive fit dey write for di customer own language by AI step, and translation wey be step inside workflow na translation wey happen for three for morning for di customer wey order at three for morning.
- ⚡ScheduleEurope/Warsaw. Yesterday window.
- 2Three sourcesShop order dem, payment provider settlement dem, accountin entry dem.
- 3Matched412 out of 416 match exactly. E deterministic; e no cost anything.
- 4Four remainAI step read di four and propose reason for each one. Person go confirm am.
- ✉Dem don send amOne e-mail. Four lines. No be four hundred.
Every day, so month-end go dullPaid steps: 1
Wetin e replace, and wetin e no replace
E replace di retyping, di reminders, di “anybody send am?”, and di four hours for start of every month. E no replace di decision about which supplier to use, di conversation with di customer wey im cake no correct, or di judgment about whether di return genuine.
E sef no replace your shop platform, your accounting software or your warehouse system. E na di thing wey dey between dem, and na di part wey nobody dey sell because e different for every business.
Make we talk am plain: shop wey dey do four orders for week no need dis one. Shop wey dey do forty na where e start to pay imsef, and shop wey dey do four hundred don already build some of am badly inside scripting language wey nobody wan maintain.