A clear stock position
Define SKUs, units of measure and locations. Show on-hand stock, reservations and unavailable quantities, with rules for when stock can be promised to a customer.
Commission a system that follows your stock from supplier receipt to customer fulfilment. Define what is available across products and locations, with the checks your team needs before promising or purchasing stock.
You can commission this system independently of Lightbulb Partners Agent. Before building, we agree the scope, data access, ownership and licensing, and how your team will test and accept the handover.
| Stock status | Units |
|---|---|
| On hand | 100 |
| Reserved for orders | 32 |
| Unavailable pending review | 5 |
| Available to promise | 63 |
100 − 32 − 5 = 63. Reserved and unavailable units are separate in this example. Your availability rules are agreed during scoping.
A system shaped to your stock
Start with the products, locations and movements that matter to your team. The first release can cover one workflow, with further capabilities added to an agreed scope.
Define SKUs, units of measure and locations. Show on-hand stock, reservations and unavailable quantities, with rules for when stock can be promised to a customer.
Scope supplier receipts, order reservations, transfers and fulfilment. Route returned or damaged goods for review before making them available again, and distinguish stock in transit from stock received.
Plan cycle counts and compare physical quantities with system records. Give authorised reviewers a way to approve adjustments, retaining the previous quantity, reason, actor, time and source reference.
Use agreed reorder levels, lead times and supplier rules to prepare purchasing proposals. Define who can approve a purchase order and how partial deliveries or changed quantities are handled.
Build, reconcile, hand over
Map one stock journey and the system that owns each record. Define which teams can view or change each location, approve adjustments and release purchase orders.
Check opening balances and mappings. Test duplicate receipts, partial transfers, cancelled reservations and returns with your users. Agree acceptance criteria and a changeover plan before release.
Agree the software, documentation and training included in handover. Define responsibility for backups, failed synchronisation and recovery. Ongoing maintenance, support coverage and improvements are scoped with your team.
Before we start
We assess the available APIs, exports, permissions and commercial access before agreeing an integration. The scope defines SKU and unit mappings, which system owns each record, reconciliation and recovery from failed or repeated updates.
No. You can commission inventory software that uses forms, business rules and human approvals. Any AI capability is optional and would have its own agreed purpose, data access and review requirements.
Project enquiries
Tell us what you stock, where it moves and which systems your team uses today. Start with one problem, such as unreliable availability, stock counts or purchasing handovers.