ERP / DEMO PROJECT
Inside the Linx ERP demo: orders, reservations and stock
This is a Linx Labs demonstration project with fictional products, customers and USD amounts. It shows how order actions can affect inventory. It is not a customer case study, a production ERP or evidence of business performance improvements.
Follow the same 2-unit order
Illustrative values for Studio Display (LX-101). Reset the demo first. Cancellation is a separate branch after creating the order.
| Action | On hand | Reserved | Available |
|---|---|---|---|
| Initial state | 32 | 3 | 29 |
| Create 2-unit order | 32 | 5 | 27 |
| Ship that order | 30 | 3 | 27 |
| Or cancel it instead | 32 | 3 | 29 |
The problem the concept explores
An order list and a stock sheet can disagree even when both look correct. A confirmed order may reserve goods that are still physically on the shelf. The demo keeps on-hand, reserved and available quantities distinct so a user can see the effect of each action.
The screens connect overview, inventory, orders and activity. We chose one small, complete workflow to make the business rules visible rather than showing unrelated dashboard numbers.
Try the stock reservation flow
Reset the demo before starting. Studio Display (LX-101) begins with 32 on hand and 3 reserved by an existing confirmed order, leaving 29 available. Create another order for 2 units: on-hand remains 32, reserved becomes 5 and available becomes 27.
Ship that new order. On-hand becomes 30, reserved returns to 3 and available remains 27. The goods were already unavailable to other orders when reserved; shipping must not deduct them twice from available stock.
- Reset the sample data and open Inventory.
- Create an order for 2 Studio Display units.
- Compare on-hand, reserved and available quantities.
- Ship the new order and check Activity.
Test cancellation as a separate branch
Reset again, create the same 2-unit order and cancel it instead of shipping. On-hand remains 32, reserved returns to 3 and available returns to 29. Cancellation releases the reservation without pretending a physical shipment happened.
A shipped or cancelled order cannot be processed again in this concept. An order cannot reserve more than available stock. Restocking increases on-hand and records the action. Search, status filters and inventory export let visitors explore the same data from different views.
What the demo deliberately leaves out
Data lives in browser memory and resets on reload or reset. The demo has no real account permissions, shared database, concurrent warehouse users, payment processing or accounting integration. Its activity view records sample actions; it is not a production audit trail.
Partial shipments, returns, multiple warehouses, tax rules and cost accounting require additional business decisions. The sample product values must not be interpreted as service prices or financial results.
How this becomes a real ERP project
A real project starts with your stock definitions, order states and user responsibilities. We would validate imports, permissions, simultaneous changes, recovery and external connections before the business relies on it.
Use the demo to identify differences from your operation. Bring a list of those differences and anonymized column examples to the scope discussion. A first phase might cover orders and inventory while keeping accounting in the current system.
TAKE IT WITH YOU
Your project checklist
- Agree on on-hand, reserved and available stock definitions.
- List permitted order transitions and who can perform them.
- Document cancellations, partial delivery and returns separately.
- Name the authoritative system for products and quantities.
- Plan permissions, concurrency and recovery before production.
- Verify trial imports and balances before replacing current tools.
Use this checklist as a starting point. Adapt it to your systems and responsibilities; it is not a completed implementation plan.