ContactBook a call

By function: Operations

Operations automation

Each order is entered once and moves through the business on that record, and the warehouse, the customer and finance hear about each change from the same event.

First workflow live
Order intake, usually inside the first sprint
Usually owned by
Operations managers and heads of ops
Built on
Airtable, SmartSuite, Supabase
Judged on
Order processing time and Re-typing

Operations automation gives every order, job or ticket one record that moves through confirmation, work, dispatch and billing with each stage updated by the system that did the work. Status reaches the warehouse, the customer and finance from the same event. SBD builds this on an operations base in your name, with a review queue for exceptions.

Where the hours go in operations

Usually brought in by Operations managers and heads of ops, Owners of a business that runs on a spreadsheet or Warehouse and dispatch leads.

Tick what is true for your team

Most teams that bring us in tick two or more.

  1. 01

    The order is typed three times

    Once into the store or email, once into the operations sheet, once into accounting. Each copy drifts.

  2. 02

    Status lives in someone's head

    Where is order 4471 is a question for one person, and when they are away the answer is nobody knows.

  3. 03

    Dispatch waits on paperwork

    Delivery notes, labels and invoices are produced by hand at the end, so the truck waits on the printer.

  4. 04

    The dashboard is last week

    Reports are compiled from exports. By the time they are read, the week they describe is over.

What we build for operations teams

Pick one to see what it does and the event that sets it off.

One order record, end to end

Enquiry to order to dispatch to invoice as one record, with each stage set by the system that did the work rather than typed in.

WhenAn order arrives from store, email or form
RunsOrder intake
ThenOne record created, validated, with the customer matched

Dispatch that notifies everyone

A status change sends the right message to the warehouse, the transporter, the customer and finance, with documents generated and attached.

WhenA status changes to dispatched
RunsDispatch notifications
ThenWarehouse, transporter, customer and finance told, documents attached

Stock and reorder visibility

Live stock with reorder flags, fed from sales and goods-in, so the count on screen matches the shelf.

WhenStock moves in or out
RunsStock and reorder
ThenLevels updated, reorder flag raised below threshold

Live operations dashboard

Orders by stage, late jobs, stock at risk and today's dispatches, read from the order record.

WhenGoods leave
RunsInvoice from dispatch
ThenThe invoice raised in accounting from the dispatch record
WhenAny record changes
RunsOperations dashboard
ThenOrders by stage, late jobs and stock at risk refreshed
Sales, enquiries, dispatch and cash outstanding: a screen from a comparable SBD build
A real screen from a comparable build.

How a operations build is judged

Each build has a target written into the blueprint, measured the same way before and after.

How operations changes from 10 people to 1,000

  1. 1 to 10people

    The owner knows where every order is, which works until the owner is away.

  2. 11 to 50people

    One operations sheet, several people editing it, and a status that depends on who last typed.

  3. 51 to 200people

    Orders in the store, stock in the ERP, dispatch on paper, and three people reconciling them.

  4. 201 to 1,000people

    Several sites, several systems, and a weekly report that takes a day to build and is wrong by Monday.

Case studies from similar builds

Know where every order is without asking

Bring one order and follow it with us from enquiry to invoice. Each place it gets re-typed is a step we can take out.

Follow one order with us
A warehouse worker checking stock on a tablet between stacked boxes
Know where every order is without asking.

What we leave out of scope

  • Replacing your ERP. We connect to it and build the work around it.
  • Warehouse hardware. Scanners and printers we integrate; we do not supply them.

Operations terms, in plain English

Order record
The one place an order’s details live. Everything else reads from it.
Dispatch event
The moment goods leave, used as the trigger for documents, messages and the invoice.
Reorder flag
A signal raised when stock crosses a threshold, with the supplier and lead time attached.

All terms in the glossary

What people ask about operations automation

We run on spreadsheets. Is that a problem?

It is the starting point for most clients. We move the sheet that became a database into a real one, keep a sheet view for the people who want it, and stop data being typed into it.

What happens when something goes wrong mid-flow?

It lands in a review queue with the record attached, and the owner is alerted so a person can make the call.

How fast is the first piece live?

The first workflow, usually order intake or dispatch messaging, is normally running inside the first two-week sprint.

Reading

Related

By function: Back office, Finance and accounting, Compliance and risk, Sales and RevOps, Customer support, Marketing, HR and people, IT, Leadership

Researching tools before hiring anyone? Read the best AI tools for logistics companies.

An audit of the operations work your team still does by hand

The audit takes one to two weeks. We map the workflows, put an hours-a-week figure on each, and give you a costed blueprint in order of payback. The audit is credited in full to the build.

  • Week 1 to 2Audit. We sit with the people who do the work and map it.
  • Week 3Blueprint, with a fixed scope and price and the first build chosen by payback.
  • Week 4 onBuild in two-week sprints, working software every second Friday.
  • After go-liveSixty days of hypercare, then a care plan or run it yourself.

Cookie preferences

Choose what this site may use on your device. You can change this at any time from “Cookie settings” in the footer.

Strictly necessary

Keep the site working and remember the choices you make here. These cannot be switched off, and none of them track you.

Always on
What this includes (4)
NameProvider PurposeDuration
sbd-consentThis site Remembers your cookie choices12 months
Vercel Web AnalyticsVercel Inc. Counts page views in aggregate. Sets no cookie and stores nothing on your deviceNone
ticker-dismissed, sbd-note-offThis site Remembers that you closed a notice or language tipUntil the tab closes
sbd-voice-resume, sbd-voice-prefillThis site Carries a voice conversation across pages, only if you start oneUntil the tab closes

Analytics

Tell us which pages are read and where visitors leave, so we can improve them. IP addresses are anonymised and nothing is used for advertising.

What this includes (2)
NameProvider PurposeDuration
_gaGoogle Analytics (Google LLC) Distinguishes visitors with a random ID13 months
_ga_FPXDMQPRV1Google Analytics (Google LLC) Keeps the session state for this site13 months

Functional

Embedded services that set their own cookies. Without them the site still works; you get a link to open the service instead.

What this includes (1)
NameProvider PurposeDuration
Booking calendarCal.com Inc. Shows live availability and books the call on the booking pageSet by Cal.com

Advertising

Not used. This site has no advertising, retargeting or social media tracking, and we never sell data.

Not used

Questions about your data: hello@smallbaydigital.com