These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Feature · Assembly and kitting
Example screen with sample data
Assembly and kitting
A released work order freezes its assembly recipe, routing, output item and planned quantity. Material issue and terminal output keep their own evidence and cost.
OverviewAssembly Schedule×
Media ERP · Assembly and kitting
New
Assembly Schedule
Projects
| Work order number | Output content item | Planned quantity | Planned start | Planned end | Manager | |
|---|---|---|---|---|---|---|
| PRJ-27607 | CI-8253 | 360 | 20 Oct | 29 Oct | ||
| PRJ-17444 | CI-6425 | 260 | 15 Oct | 18 Oct | ||
| PRJ-93326 | CI-4798 | 360 | 11 Oct | 16 Oct | ||
| PRJ-65650 | CI-7695 | 410 | 17 Oct | 26 Oct | ||
| PRJ-91877 | CI-3653 | 740 | 14 Oct | 22 Oct |
6 of 6 records
CI-8253Projects · PRJ-27607
ReleasedPlanned quantity360
Planned start20 Oct
Planned end29 Oct
What you can do
Assembly and kitting in daily work
A released work order freezes its assembly recipe, routing, output item and planned quantity. Material issue and terminal output keep their own evidence and cost. The team keeps each handoff tied to its source record so changes to a later step do not quietly rewrite the earlier decision.
A warehouse team combines separately stocked items into a saleable kit. The manager chooses an active assembly and route, reviews the planned output, then releases the project. The operator records actual material use and completed output. Keep the approved revision with the work. When circumstances change, record the correction or next decision against that version.
How the work is organized
- Define. Warehouse Manager selects the effective assembly, route and standard cost basis.
- Release. Warehouse Manager checks planned output and available components before work starts.
- Complete. Warehouse Operator records actual material and output; Finance Manager reviews residual variance at close.
The preparation and execution records answer different questions. A planned quantity describes intent; a posted movement, accepted receipt or confirmed payment describes what actually occurred. Keep both when comparing what was promised with what happened.
What to agree during setup
Agree the output basis, allowable scrap, work steps, labor evidence and standard rate. Name the manager who may release work and the finance owner of variance review. Document the decision owner for each exception. Give users only the entity and location scope they need. Use a pilot with an ordinary case and a partial or failed case before allowing routine work to depend on the configuration.
The item code and customer or supplier identity should stay stable during migration. Where a document carries a currency or unit conversion, retain the applicable version with that document. A later master change should apply to future work, not change an accepted transaction.
Check the handoff on an actual case
Run a kit whose output is below plan. Confirm issued and returned material, terminal output and remaining work in process. Close only after residual variance is resolved through the reviewed path. Ask the preparer and decision maker to review the same case separately. Compare the source quantity, the actual recorded quantity and what remains available for the next step.
The receiving team should be able to explain why the record is ready, what still needs review and who owns the exception. Rehearse a repeat submission and a changed source after approval. Keep the original evidence visible when the case is corrected.
What your team sees
- Assembly Schedule — See released work, planned dates and actual completion state.
- Available Stock — Check component positions before reserving material.
Follow the work through
Follow the connected process, then review the record map and access rules.
What it keeps track of
Data model- Content assemblies
- Effective distribution assembly/repacking recipes with explicit output basis.
- Assembly components
- Component quantities per explicit output basis, preserving dimensions and allowed loss.
- Production workflows
- Versioned assembly/repacking instructions, distinct from delivery routes.
- Workflow steps
- Ordered work instructions and declared labour/overhead bases.
- Projects
- Released bounded assembly/kitting/repacking, without plant APS or payroll scope.
- Production tasks
- Frozen instructions and assigned actual work.
- Production materials
- Frozen required input and actual traced issue/return scope.
- Production entries
- Actual operation throughput, scrap and labour evidence; intermediate counts do not sum to output.
- Production completions
- Accepted terminal output and WIP cost allocation, once per actual completed scope.
- Project costs
- Immutable WIP debit/credit sources and bounded actual-cost allocation.
Who uses it
Permissions- Warehouse Manager
- , Warehouse Operator and Finance Manager.
- Each person acts within their assigned entity and work scope.
Set up Media ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.