Build an orders and production board

Build a native Tauri application that turns customer orders into a manageable day's work. It should connect what was ordered, what needs preparing, and what has been completed. Build it extremely well for the person doing the making. An explicit framework preference takes precedence over Tauri.

Follow the shared launch. Learn what the person makes and how an order moves from agreement to collection or delivery. Use their work to shape the app. For someone exploring the idea, use a small home bakery as the starting example, with ordinary batches and a few custom orders.

Understand the work before drawing the board

An order begins with a customer's request, but making it involves other decisions. What has been agreed? Is a deposit due? When does preparation need to start? Which orders can be made together? What must be finished separately? Learn the answers through a representative working day.

For the bakery example, Saturday's orders might include several boxes of the same cookies and a decorated birthday cake. The baker wants the combined cookie quantity for preparation and each customer's quantity for packing. The cake has its own message, decoration, and promised collection time. Preserve those differences.

Give an order a clear customer, contents, agreed details, price and payment record, and deadline. Keep notes and relevant reference material with the work. Let the person adjust these to the actual things they sell and the decisions they make.

Show the work at the right level

Make it easy to enter an order while talking to a customer, inspect its details later, and see what needs attention today. Let the person organize production using stages that reflect their work. They should be able to record partial progress, find an urgent order, and see what still needs making or packing.

Generate preparation and material lists from the same orders. Use the quantities, units, and production rules the person supplies, making the calculation understandable. Where batching matters, show how a batch relates to the orders it will fulfill. They can change the working plan when equipment, materials, or time require it.

Keep the customer's promised collection or delivery time visible alongside the internal preparation plan. A useful board helps the maker decide what to do next and explains why a job needs attention before its delivery date.

Handle changes after work has started

Imagine that a customer increases an order after part of the batch is already prepared. Keep the completed work recorded, update what remains, and make the change visible where it affects preparation and packing. A cancelled order should likewise have an intelligible effect on the remaining workload and the person's payment records.

Support corrections without making the person reconstruct the order from memory. Keep enough history to answer what changed and which agreement is current. Give deposits, remaining balances, and refunds their appropriate meaning in the person's recordkeeping. Record payments in the app; actual payment collection can continue through the methods they already use.

Take it through one working day

Make the result useful on the installed desktop app, including saved work, recovery, and practical printed or exported order sheets when the person needs them away from the screen. Their production records should remain theirs under the shared launch's ownership arrangements.

Work through several representative orders together, combine a preparation quantity, begin work, change one order, and complete the packing or handoff. Judge whether the person can rely on the board without maintaining a second private list to make sense of it.

Explain how one order can supply a customer record, preparation list, and work schedule. That relationship is what removes the repeated copying. Later projects can add a phone view for recording progress or another person's participation while retaining the orders and completed work already here.