Guides

Kit Materials and Consignment Stock Management

Kits collapse BOM into one card while components issue separately. Consignment sits on your shelf but stays vendor-owned until usage is invoiced.

Published:11 min read
Kit Materials and Consignment Stock Management

When to use kits

Field service sets and filter kits order as one SKU but stock as components. kit part flag with PartKitComponent holds the BOM.

Kit on-hand rises only via assembly—component OUT, kit IN. kit explosion splits kits on pick lists.

Assembly and disassembly

Assembly cost sums component issues into kit receipt; short components return four zero nine with meta. Nested explosion up to five levels with cycle check.

Disassembly reverses: kit OUT, components IN. Build qty capped by buildable quantity.

Consignment logic

Consignment receipt sets isConsignment; consigned quantity rises while vendor retains ownership.

applyConsignmentOnOut consumes consigned qty first and logs consignment usage record for invoice prefill.

Consignment billing

Procurement > Consignment tab and consignment report show open usage and consigned quantity by vendor.

Usage invoices may match without PO if sourced from consignment usage record.

FIFO versus average

costing method AVERAGE or FIFO. AVERAGE updates weighted avg; FIFO opens cost layer and consumes layers on issue.

AVERAGE to FIFO converts existing stock into one opening layer. Layers are part×warehouse, not lot-level.

Reading kit cost

Assembly rolls component issue cost; under FIFO each component layer consumes separately. Average uses component avgCost.

cost-layers report shows FIFO layers; stock value report labels the method.

Work orders and picking

Work-order kit lines explode to component reservations; short components block assembly. Issuing kit without assembly skews stock.

spare parts inventory module work-order issues and warehouse and inventory management kit engine share movements; consignment billing is a separate trail.

ERP export note

Kit and consignment movements map to LOGO, NETSIS or GENERIC CSV export types—align mapping with project accounting.

Roles and kit/consignment rhythm

Warehouse leads assemble kits only when components suffice; shortages return API meta.

Procurement marks consignment GR; verify consigned quantity against vendor agreement.

Finance changes costing method at period start; AVERAGE to FIFO opens one layer for existing stock.

Work-order kits explode to component reservations; do not issue kit card directly.

Additional practical notes

Nested kits explode up to five levels; cycle check blocks bad BOMs.

Disassembly reverses movement; scrap kits with a separate code.

consumeConsignedFirst issues consigned qty first; cost trail until invoiced.

prefill-consignment fills invoice lines from consignment usage record tied to the invoice.

FIFO layers are part×warehouse; lot cost is not layered.

cost-layers validates FIFO value; AVERAGE shows avgCost in report headers.

Map kit assembly movement types in ERP export to project accounting.

Reconcile with vendor when consignment clears; no open consignment usage record.

Audit readiness

Audit kit assembly as paired component OUT and kit IN; rolled cost must match component avgCost or FIFO layers before build.

Reconcile consigned quantity monthly with vendor statements; gaps point to consignment usage record or GR flag errors.

Do not change costing method mid-period; attach FIFO cost-layers report to period close.

kit explosion pick lists return 409 meta on component shortage—treat as early warning in audits.

Auditors ask for mapping table linking kit/consignment export types to project GL codes in GENERIC CSV.

Sustainable improvement cycle

At month-end, review replenishment, invoice match, lot expiry and kit/consignment reconciliation together—if one module KPI breaks another, root cause is joint. Mass feeds this from one movement ledger.

Name approvers for each exception type: variance invoice notes, quarantine lot release, kit assembly shortages, consignment period invoices. Track exception rate monthly.

Negative stock, unmatched invoice lines and EXPIRED lots clustering on one warehouse code in the same week triggers bin or unit review before blaming software.

External audit pack: saved count session summary, matched/variance mix, FEFO strict violation sample, kit cost tie-out, consignment consigned quantity closure—PDFs linked to supplier invoice record and receipt lines.

Onboard staff with fifteen-minute demos of import templates, Order Suggestions page filters, invoice wizard and lot labels; supervised first week instead of certificate-only training.

At project close, clear draft purchase order, unmatched invoices, QUARANTINE lots and open consignment usage record before team disperses—checklist mirrors Mass onboarding card on the dashboard.

Operational decisions rely on one ledger—replenishment, invoice tolerance, FEFO and kit assembly readiness no longer use side spreadsheets.

Each KPI owner commits one improvement next month; if missed, fix the process not the target.

Flows match shipped Reper Mass behaviour; (count lot picker, digest language) reflect the current release.

Audit trail and invoice actions answer who/when from one source.

Kit and consignment share the same warehouse movement ledger.

Frequently asked questions

Do you order kits

Usually order components; kit card simplifies on-hand after assembly.

Who owns consignment

Vendor until usage is invoiced and consigned quantity clears.

FIFO with lots

No—layers are part×warehouse, not lot-level.

Request a Mass demo for kit assembly, consignment tab and FIFO cost layers.

Request a demo