What the platform does.
Seven areas over the same data. What each one solves, and what the platform deliberately does not do.
From the request to the production line.
An order belongs to a customer and its lines are items or packs. Each line carries quantity, size, price and, when the item allows it, per-piece personalisation.
- Packs sold as a whole, produced piece by piece
- Personalisation per unit: name, number, whatever the item defines
- Generic items and items exclusive to one customer
- Per-customer prices, on top of the base price
- Four ways in: office, catalogue, club store, importer
Deciding what to make and what to take from stock.
Before anything is sent to the floor, the release screen shows line by line how much free stock already serves that order. The amount to use is set there, and the floor only makes what is missing.
- Free stock by item and size, in view at the moment of the decision
- What is assigned is reserved without leaving the inventory
- A line covered in full is completed without reaching the floor
- A warning when the order is prepaid and still unpaid
Planning against the capacity that exists.
Each production order is split into dated parts. The work calendar knows the working days and each one's capacity, and the floor board shows the work for the day.
- Work calendar with capacity per day
- One order split across several days
- A production board readable on the factory floor
- PDF production sheet carrying each piece's personalisation
- Quality checks per item
A ledger, not a balance.
There is no current-stock column. There are movements, and the balance is their sum. That is what makes the inventory at a past date available with the correct answer.
- Locations and positions, with put-away as a transfer
- Manual entries and exits on their own document
- Free stock and stock assigned to an order line
- Automatic entry when production completes, exit when it ships
- Inventory exportable at any date
What leaves, where to and with whom.
The shipping board shows what is ready. Each delivery produces a packing list and has a defined destination: the factory, the customer address, or the address of whoever bought in the store.
- Partial deliveries, as many as needed
- Packing list carrying each piece's personalisation
- Factory pickup, ship to customer, or dropshipping
- Carrier and tracking number per shipment
Every customer with a shop window.
A public address per customer, in their colours, where members buy and personalise. What comes out of it is an order like any other.
- A catalogue per customer, with or without the generic items
- Personalisation done by whoever is buying
- Spreadsheet import, for orders with dozens of names
- Ship to the club or straight to the buyer
Charging for what was delivered.
Payment notes copy the lines they cover, and receipts sit on top of them. On credit terms they go out with each delivery; on prepayment they are issued on demand.
- Notes per delivery, or on demand over what is still to bill
- A second note picks up the lines added after the first
- Cancelling a note returns its lines to what is still to bill
- Partial receipts and a per-customer account
What this is not.
It is not an ERP and not accounting software, and it does not aim to be. It does not issue tax-certified invoices: it issues payment notes and internal receipts, and exports what accounting needs. It does not handle payroll or attendance. It does one thing: take a custom order from the request to shipping.
Trial it with real orders.
Thirty days with the whole platform, no card. A company name and a contact are enough.
30 days · no card · nothing to install