SemutzFMCG OS
Book a Demo
Book a Demo
Platform

One system, four products. Not four silos with an integration bill.

Semutz runs as a single multi-tenant platform. SFA, WMS, TMS and ERP are surfaces over one shared master data layer, one permission model and one audit trail.

One

One SKU record

Item, pack, batch rules and storage profile defined once.

One

One customer record

Credit limit, terms, route and outlet channel, shared by sales, dispatch and finance.

One

One document trail

SO → DO → Trip → Invoice linked end to end, with immutable history.

One

One permission model

Roles by site, warehouse, route and product, not per-app logins.

A day in the life of an order

Follow one order, see every product work

The same record moving through the same database: one row of truth, six handoffs, no re-keying in between.

  1. SFA
    06:40 · SFA

    Sales order

    SO-70914 for MK Supermarket, priced from its price group and checked against its AR credit.

    SO-70914
  2. WMS
    07:05 · WMS

    Stock allocated

    FEFO picks the oldest eligible batches; short lines flagged before the pick starts.

    DO-88214
  3. WMS
    07:52 · WMS

    Picked & packed

    Scan-verified pick down racks A→B, cartons labelled for stop sequence.

    PKG-3391
  4. TMS
    08:05 · TMS

    Loaded & dispatched

    Capacity check against 18/20 pallets, trip sheet released to the driver app.

    TRIP-2210
  5. TMS
    09:12 · TMS

    Delivered

    Driver captures POD at the door; 2 short cartons coded as a return.

    POD-77120
  6. ERP
    09:15 · ERP

    Invoiced

    Invoice posts against the delivery, short-pick credited, ledger updated.

    INV-44120
Integration approach

API-first, documented, boring on purpose

Your finance package, your e-commerce channel, your principal's EDI feed and your handheld scanners all talk to the same endpoints. Nothing is locked behind a screen only one vendor can configure.

  • REST & GraphQL endpoints over shared master data
  • Webhooks on document events (SO, DO, POD, invoice)
  • Bulk CSV / EDI import for customer, item and price masters
  • Sandbox tenant for your team to build against before go-live
POST /graphql · application/json
# Allocate stock for a confirmed order query { salesOrder(ref: "SO-70914") { customer { code name route creditLimit } lines { sku description qtyOrdered allocation(strategy: FEFO) { bin batch expiry qty } } deliveryOrder { ref status } } }
Migration path

From spreadsheets and legacy point tools

Week 1

Map what you have

We take your item list, customer list, rack layout and current price lists. Where the data disagrees with itself, we show you the conflicts before anything moves.

Week 2

Clean master data once

Deduplicate SKUs and customers, agree pack sizes and storage rules, load the shared layer. This is the step most projects skip, and it's why ours don't stall.

Week 3

Run one process live

Usually goods-in or order capture. Your team uses the real screen on the real floor while the old method stays available in parallel.

Week 4+

Add the next product

TMS or ERP follows on the same data. No second migration, because there is nothing to migrate: it's already the same database.

Questions ops teams ask

Before you book the demo

Do we have to move off our current accounting software?

No. Semutz ERP handles order-to-invoice and operations-side financial documents, then posts to your accounting ledger through a supported integration. If you already run a finance package you trust, we keep it and feed it.

What happens to our spreadsheets?

They become imports. We take them as they are, flag what can't be trusted, and give your team read-only reporting out of the system so the spreadsheet stops being the operational record.

Can we run one product without the others?

Yes. SFA or WMS can run standalone with a light master data set. The moment you add a second product, the shared layer is already in place; that's the difference from stitching point solutions together.

How is the deployment hosted?

Cloud-hosted, multi-tenant, with per-tenant data isolation and role-based access by site, warehouse, route and product. Production and sandbox environments are separate, with audit history retained on every document.

What about devices on the floor?

Warehouse screens run on standard Android handhelds and tablets; the driver and rep apps run on Android and iOS. No proprietary hardware purchase is required to go live.

Bring your messiest data to the demo

Rack list, item master, price list, whatever state it's in. Seeing the platform work on your real data beats any slide about it.

Book a Demo Explore Products