A location needs stock
Someone raises a replenishment request for exact supplies and quantities.
A proposed way to follow paper, media and frames from request to delivery, then estimate what remains as the kiosk prints.
This is not a warehouse-management programme. Most supplies go directly to a venue. Storage exists only for the cases where TheArtisan or a partner temporarily holds stock.
Kiosks use supplies. Locations hold supplies. A warehouse is only another possible place that can hold them.
Meeting goal: identify where this picture differs from the way distribution actually works.
The normal flow is intentionally simple. A request can be split into several deliveries, and a delivery can be confirmed in more than one pass.
Someone raises a replenishment request for exact supplies and quantities.
One request may become one or several supplier or internal deliveries.
Tracking, supplier reference, expected date, cost and documents stay with the delivery.
They confirm what was accepted and separately report what was damaged or missing.
Only confirmed accepted quantities increase the location's stock estimate.
Each recorded physical print subtracts its known paper and frame recipe.
The database does not decide the organisation. It records what each person or system has already decided or observed.
The recipe is configurable per printer setup. These three cards show today's known patterns, not permanent limits.
A single portrait consumes one 4x6 print-equivalent and one physical frame.
The print is still exactly 4x6. The combi frame only changes how portrait or landscape orientation can be presented.
The physical printer may be the same, but the output consumes twice the media and requires a larger frame.
Can supply a 4x6 output. It cannot supply a 6x8 output.
Can supply both 6x8 and 4x6 outputs. The selected recipe records which physical item is used.
The result is an operational estimate. It becomes more accurate whenever someone confirms a delivery, records waste or accepts a physical reconciliation.
The history is append-only. A correction adds an exact reversing entry instead of silently rewriting an old fact.
What the location says it accepted into usable stock.
The exact expected recipe for that print format and printer setup.
Jam, loading waste, damage found after acceptance or supplies lost.
A human accepts a difference after a real count or credible printer reading.
Which prints are billable comes from recorded prints and transactions. Stock never decides what a venue owes.
Stock answers a different question: how much usable material should remain, and when should distribution investigate or replenish it.
This example uses one compatible media item. Frames would be calculated separately in exactly the same way.
The damaged and missing claim is evidence for the supplier dispute. It does not enter stock because the venue never accepted those units.
Click a box when the proposed behaviour matches reality. Leave it open when the answer is unclear or different.
Leave the meeting with the normal route confirmed, every exception named, the responsible person identified, and the units that people naturally use written down.
Nine tables preserve the operational facts. The split exists only where the real world contains several lines or repeated events.
Exact media and frame products, units, compatibility and default package conversion.
One pool per location, plus occasional Artisan or partner storage.
A request and its individual supply lines, including the package quantities entered by a person.
Supplier or internal source, destination, tracking, documents, quantities and latest damaged or missing claim.
Reusable recipes linking a physical output to exact media and frame quantities.
Receipts, print consumption, transfers, waste, adjustments and exact reversals. This append-only history is the stock truth.
No racks, shelves, bins, picking waves, reservations, complex ownership or warehouse routing. The operation does not currently need them.
Retries cannot duplicate stock, old events cannot be edited, recipe quantities are exact, and later configuration changes cannot rewrite historical meaning.