Every parcel goes out through Sebity.
It sits between Cin7 Core and StarShipIt and owns the whole bench: the checks before the label prints, the label itself, part shipments, the write-back to Cin7, and the reconciliation that tells you what the carrier actually charged.
In production since July 2026, across five packing benches, as the only way parcels leave the building. Built by an operator who still packs the boxes. Founding tenant: Personalised Favours, a Sydney personalised-gifts business.
Cin7 and StarShipIt aren't built to talk to each other this way.
The direct integration moves orders across. It doesn't catch what changed between the order and the box, and it can't tell you afterwards what any of it cost. These are the ones that take money off you.
The address changes in Cin7 and doesn't follow.
The parcel ships to the old address. The customer messages you when it doesn't arrive. You re-ship, plus the apology.
Pickup orders get shipped by mistake.
The order was marked customer collection. It still ended up on the dispatch run. Now there's a parcel in transit nobody meant to send.
Express orders ship Regular.
You promised Friday. They get it Tuesday. The service downgrade is invisible until the one-star review lands.
Items go missing from packed boxes.
The customer opens the parcel and calls support. You can't tell what was in the box or who packed it. There's no trail to follow.
The carrier's invoice is the first you hear of it.
Surcharges, re-weighs and articles lodged without a manifest land weeks later on a PDF nobody has time to check line by line.
Nobody can say what an order is waiting on.
Artwork? Payment? Stock? The answer lives in somebody's head, or in a shared inbox, and it changes depending who you ask.
Sebity owns the moment before the label prints.
The operator scans the packing slip. Everything below happens before anything is committed to a carrier, while the person is still standing at the bench holding the box.
It re-fetches the latest address at the scan.
The instant the operator scans, Sebity pulls the current Cin7 address. Stale data can't reach the carrier. If it changed after the order was placed, the right address still wins.
Pickup, cancelled and held orders can't ship.
The scan refuses. The operator gets a plain screen that says why, in one line. Nothing leaves the bench by accident, and nobody has to remember the exception in their head.
Every parcel is weighed against what's in it.
Sebity compares the weight on the bench scale to what the order should weigh, built up from the bill of materials for what is on the order. A light box stops before the label prints, so a missing item is caught at the bench and not by the customer.
Ship what's ready. Or ship it in four boxes.
An order can go out in parts, or as one order across several consignments, each with its own label and tracking. If the same customer has more than one order on the bench, Sebity raises it and offers the three-way choice: pack together, ship separately, or hold the lot.
What it does, now that it runs a real dispatch floor.
The bench was the wedge. Since going live in July, Sebity has taken on most of what surrounds it, because every one of these started as something an operator was doing by hand or finding out too late.
At the bench
- Scan to labelCarrier and service resolved automatically, live weight from the bench scale, silent print to the station's thermal printer.
- Station hardwareA local helper on each packing PC drives the scale, the printer and the barcode input, and reports its own health to admin.
- Box dimensions and carton presetsFor the carriers that charge on cube rather than weight.
- Delivery instructions and signature on deliverySet per order, carried through to the carrier.
- Void and re-shipIncluding the case where the carrier accepted the consignment and the system never heard back.
Carriers, rules and customs
- Editable carrier rulesBy destination, by state, by address pattern, by customer. Pause a carrier with one button when they are having a bad week.
- Forced carrierCustomer service can override the carrier on a single order. If that carrier doesn't serve the destination at the speed the order implies, Sebity takes their other speed and says so, rather than stopping the bench.
- Unmapped service warningA shipping method with no rule behind it raises a warning when the order arrives, not when someone is standing there holding the box.
- InternationalDHL Express as a mapped carrier, declared customs values, receiver tax and EORI numbers carried on the order.
- Supplier shipmentsThird-party dispatches recorded straight into Cin7 without passing the bench.
After the label
- Freight invoice reconciliationThe carrier's bill against what Sebity recorded, line by line, so a re-weigh or a surcharge is something you find rather than something you pay.
- Failed Core update reportShipped parcels whose fulfilment never made it back into Cin7. The report exists so no order sits shipped and unrecorded.
- Missing itemsA remediation trail from the weight that stopped at the bench through to what was done about it.
- ReplacementsWhat is being re-shipped, what it cost, and which base products keep coming back.
- Overdue ordersTwo derived worklists with owners and last action, instead of a spreadsheet somebody maintains.
The order itself
- Order stageA derived answer to "what is this actually waiting on", rather than a status somebody has to keep up to date.
- Payment as a production gateWith account customers as the documented exception, not a workaround.
- Artwork and personalisation at line levelOn the same order page the dispatch team uses, so both teams are looking at one record.
- Stable line numbersA line keeps its identity when the order is re-read from Cin7, which is what makes any of the above safe to act on.
Channels
- Cin7 CoreWebhook ingest with a reconciliation sweep and a drift check behind it, paced inside the account's call budget. A gap of any length heals on the next run.
- EtsyOrder intake, dispatch write-back with tracking, and an automatic void in Cin7 when a buyer cancels.
- Etsy stock actionsA queue that reads the listing and asks, rather than writing quantities at a marketplace and hoping.
- API budget meteringEvery marketplace call counted, with a reserve held back for the work a buyer would notice.
Reporting
- Scheduled management reportsWeekly and monthly, as branded PDFs, mailed on a schedule from your own domain.
- Recipients per reportSet in admin, with a test send and the last sends visible, so nobody is chasing who gets what.
- Built from the source systemsRevenue, orders, despatch timing against the promised date, and labour, drawn from the ledger and the dispatch record rather than re-keyed.
- Every number explainedEach report carries a section saying how its own figures are built, because a number nobody can derive is a number nobody trusts.
Roles, access and audit
- Roles you createNot a fixed ladder. Build the role, choose the pages it can open.
- Every write auditedNamed actor, field-level before and after, on every operational table.
- Two ways inEmail and password, or Google Workspace sign-in locked to your own domain.
- Bench tabletsKiosk-locked logins and session policies for the machines that live on the floor.
- Credentials encrypted at restCarrier and marketplace keys in an encrypted store, never in a config file.
Multi-tenant from the first table
- Tenant isolationEvery operational row carries its tenant. It was built that way on day one rather than retrofitted.
- Your own carrier accountsSebity uses your StarShipIt and Cin7 accounts. It doesn't resell freight and doesn't sit in your ledger.
- Separate environmentsA staging environment that mirrors production, and a deploy path that is written down.
- Visitor registerDigital reception sign-in and sign-out, because the floor came with a paper book.
Why Sebity, and not a generic OMS.
Most order-management software is built for plain e-commerce and retrofitted to everything else. Sebity is built the other way round.
Built for personalised and made-to-order.
The data model knows what an artwork-pending order is, what an embellishment SKU is, and how a multi-component bundle ships. It isn't a retail OMS pretending to understand custom work.
It sits inside the stack you already run.
Sebity doesn't replace Cin7. It doesn't replace StarShipIt. It doesn't touch your ledger or your carrier accounts. It slots between them and owns dispatch, and nothing else changes.
Built by an operator, not a vendor.
Sebity was built by someone who still picks orders during peak. Every check in it exists because the absence of that check once cost a real parcel and a real customer.
Every feature has an incident behind it.
The weight check, the manifest watch, the carrier fallback, the freight reconciliation: none of them were on a roadmap. Each one is the answer to a specific day that went wrong, and the reason is written down next to the code.
Where it actually is.
Everything above is live in production and used every working day. Here is the rest of it, including the parts that are built and deliberately switched off. We would rather you heard it from us than found it in a demo.
Customer tracking notifications
Sebity sits between the carrier and your email platform, so a parcel that reports two statuses can only ever produce one email, the customer sees your order number rather than the accounting system's, and a collected pickup gets a receipt with the name and signature of whoever took it. The code is deployed. Every event ships disabled and stays that way until a person throws the switch alongside the matching email flow, so no customer has been sent anything by Sebity yet. The same build puts the carrier's own scans against the order in your database, where reporting can reach them.
Manifest watch
An article lodged without a manifest is billed at a penalty rate and nothing tells you until the invoice. Sebity now watches for a parcel that printed a label and never made a collection, and for one archived while still holding a label. It is running and being proved against real manifests before we claim it.
Artwork workflow
The job model, the queue and the artwork section of the order page are in production, running alongside the shared inbox to prove the model. The customer approval portal, with proof upload and amendments, is built and sitting in staging. Not released, and not replacing anybody's inbox yet.
The second tenant
A second business is being brought onto Sebity: their import, their sale creation, their dispatch from their own carrier account, their invoicing and their reporting are all on production behind switches that are still off. Not one of their orders has been created, labelled or invoiced yet. When it has, this paragraph will say so.
Production workflow and parametric artwork
Taking over production routing, BOM execution and work-in-progress tracking, and generating artwork from templates so a customer can preview it themselves. Designed, scoped, not built. We will not sell you either of them today.
One customer, most of a second. We'd rather be honest about it.
Sebity's founding tenant is Personalised Favours, a Sydney personalised-gifts business. It has been the exclusive dispatch path there since 29 July 2026, across five benches, through Father's Day. A second business is onboarding now. That is the whole customer list, and we would rather show you one real packing bench than a wall of logos that never shipped a box.
What we still can't claim: Sebity has never been installed by anybody who didn't build it, and it has not been through a November. Both of those are coming, and you will read about them here either way.
Tell us what you run.
Sebity isn't self-serve yet. Tell us what's in your stack and how many orders go out the door. Pricing depends on volume, and we'll talk it through. No sequence, no pressure.