Sales
The Sales module is the other side of purchases: what you sell. Customers, sales orders, and their line items.
The loop:
- Pick a customer (or add one).
- New sales order: a customer, a number, and line items.
- Fulfil it. Stock drops, and the low-stock view tells you what to reorder.
Customers
A customer is a record: a name, and optionally email, phone and address.
- Open one to see their orders and history, edit in place, and delete when they are gone.
- The customer list is where a sale starts when the buyer is a repeat one.
Orders
New sales order takes a customer, a number, and line items.
- Each line's search box looks through your inventory parts as you type, and also takes free text, so you can sell something you never tracked without inventing a part for it first. A line linked to a part is tied to the actual stock it draws from.
- Status: draft, shipped, fulfilled, or cancelled, alongside its order date.
- Nothing touches stock until fulfilment, so a draft is safe to edit and a cancellation costs nothing.
- Cobb can add a line to an order you already raised. Removing one stays in the app on purpose, because an order is a financial record.
Fulfil and decrement
Fulfilment is the one step that touches stock.
- Each line linked to a part decrements.
- The order stamps its fulfilled date.
- Free-text lines pass through untouched, since there is nothing to decrement.
Who this is for, and the storefront hook
Fulfilling an order takes the sold parts out of stock, so the loop closes itself: sell, fulfil, stock drops, and the low-stock view tells you what to reorder. It's built for makers and small shops selling finished goods, sitting on the same inventory that Purchases and Builds feed.
Orders can also be created programmatically through an action, which is the hook for a storefront: the shop calls your instance, the order lands as a draft, and fulfilment stays a human step.