Appearance
Production Operations
Production operations convert demand and materials into finished output. Use the Production menu for generic manufacturing work, even when an industry pack such as Apparel supplies the terminology or templates.
Production operations provide manufacturing context and execution orchestration, but they do not replace the shared owner ledgers for documents, stock, inspections, billing, payments, or reporting.
Open Production -> Operations.
Production Control Center
The grouped Production Operations lanes open with a Production Control Center above the detailed workspace tabs. This is the operator/planner cockpit: it does not create a second production ledger, but it tells the user what the next best action is, what blocker to check, and which shared primitive owns the work.
Use the lane cards as the daily operating sequence:
| Lane Card | Primary Question | Owning Primitive |
|---|---|---|
| Document control | Is the quotation, sales order, procurement order, receipt, or dispatch document approved and traceable? | Document Transactions |
| Plan demand | Have MRP/MPS, shortages, suggestions, pegging, and exceptions been reviewed? | Production Planning |
| Capacity gate | Are machines, tools, labor pools, maintenance, calibration, downtime, and bookings ready? | Resource Capacity |
| Release work | Does the production order have the correct BOM, routing, source demand, material plan, and quality gates? | Production Orders |
| WIP control | Are operation handoffs, holds, scrap, rework, returns, and completions reconciled? | Production WIP |
| Quality gate | Is inspection evidence approved and are NCR/CAPA or hold decisions closed? | Inspections |
| Dispatch work | Is output accepted, available, packed, documented, and ready for customer handoff? | Dispatch and Inventory |
| Follow-up | Is downstream billing, costing, settlement, payroll, or reporting complete? | Billing, Costing, HR, Payments, Reporting |
QA should treat the cockpit as the user’s first stop for a production lane. The expected behavior is:
- every visible card corresponds to a permission-visible tab or linked workspace
- clicking an embedded lane focuses the matching tab without losing route context
- clicking a follow-up lane opens the owning workspace rather than duplicating its UI
- the user can identify release blockers before opening a form
- the text references business risks such as approval, source lines, materials, capacity, QC, WIP, costing, and dispatch readiness
Production Order Control Center
Inside a production order detail, the Production Order Control Center is the closeout cockpit for that one order. Use it before editing detail tabs or attempting output completion/closure.
It summarizes six gates:
| Gate | What It Tells The User | Detail Tab |
|---|---|---|
| Release Gate | Whether source demand, engineering handoff, and release checks are passed, pending, blocked, or overridden. | Materials |
| Material Reconciliation | Whether raw materials still need reservation, staging, issue, return, scrap/waste, or WIP disposition. | Materials |
| Operations & Labor | Whether operation lines are planned, in progress, blocked, complete, or missing labour/resource evidence. | Operations |
| Quality & Output | Whether QC holds, missing approved inspection evidence, NCR/CAPA, or output receipt blockers remain. | Output |
| Costing & GL | Whether production cost evidence is captured, posted, failed, or still waiting for Post Costs retry. | Costing & GL |
| Closeout Readiness | Whether the order can be closed or which blocker must be resolved first. | The blocker tab |
QA should verify that each card moves the user to the relevant detail tab and that closeout warnings do not rely on users manually reading every line. The order is not production-grade if users can complete output or close work without seeing material, quality, operation, and costing blockers in one place.
Standard Flow
| Step | Workspace | Business Meaning |
|---|---|---|
| 1 | Quotations | Offer manufactured goods or services to the customer through shared document context. |
| 2 | Sales Orders | Capture confirmed demand through shared document context. |
| 3 | Production Planning | Run MRP, review shortages, and create supply suggestions. |
| 4 | Procurement | Order missing inputs. |
| 5 | Material Receipts | Receive accepted inputs into stock through shared inventory consequences. |
| 6 | Production Orders | Plan and release factory work. |
| 7 | Resource Planning | Create capacity slots, reserve resources, and confirm readiness controls. |
| 8 | Shop Floor | Record operation progress, scans, labor, and output. |
| 9 | Quality Control | Inspect WIP or finished output through shared inspection evidence. |
| 10 | Dispatch | Release approved finished goods through shared document and inventory consequences. |
| 11 | Billing | Invoice delivered output, apply deposits, collect the remaining customer balance. |
| 12 | Production Costing | Reconcile material, labor, overhead, WIP, scrap, rework, output, and variance. |
| 13 | HR Payroll | Review payable operator labour, run payroll, and pay employees through payment batch. |
| 14 | Reporting | Confirm production, stock, billing, payroll, costing, and GL reports agree. |
School Uniform Example
For a school-uniform manufacturer, the Apparel/Garments category may provide defaults such as style terminology, size/color templates, garment QC checks, and label formats. Users still work through the same Production flow:
| Flow Step | School-Uniform Example |
|---|---|
| Quotation | Quote shirts, tunics, trousers, sweaters, logo embroidery, and delivery terms. |
| Sales Order | Confirm quantity by school, size, color, and delivery date. |
| MRP | Calculate fabric, thread, buttons, labels, packaging, and shortage actions. |
| Procurement | Order missing fabric, trims, labels, and packaging. |
| Material Receipt | Receive approved fabric and trims into stock. |
| Production Order | Release cutting, sewing, branding, QC, and packing work. |
| Shop Floor | Track bundles, operation progress, scrap, rework, and partial output. |
| Quality Control | Check measurements, stitching, logo placement, stains, and packing accuracy. |
| Dispatch | Deliver approved finished uniforms to the school. |
| Billing | Apply the school deposit, issue the delivery invoice, and clear the balance. |
| HR Payroll | Pay cutting, sewing, branding, QC, or packing operators from labour evidence. |
| Costing | Review material, labor, overhead, scrap, rework, and variance. |
See Manufacturing Industry Categories And Examples for the full school-uniform walkthrough and additional food, plastics, metal, roofing, furniture, and assembly examples.
Operations Form Reference
These forms are shared across manufacturing categories. Category packs may change labels or defaults, but the business meaning stays the same.
| Workspace | Form Meaning | Key Fields To Review |
|---|---|---|
| Quotations | Commercial offer before confirmed production demand. | Customer, product design/item, variant, quantity, price, delivery date, terms. |
| Sales Orders | Confirmed demand that can drive MRP. | Customer, due date, delivery location, order lines, linked quotation, approval state. |
| Production Planning | Material and supply planning run. | Business unit, horizon, warehouse, item scope, planning mode, included demand flags. |
| Procurement | Purchase or replenishment for missing inputs. | Supplier, material/component, quantity, expected date, receiving location, price. |
| Material Receipts | Accepted inbound materials received into inventory. | Supplier, receipt lines, accepted/rejected quantity, warehouse, QC state. |
| Production Orders | Planned or released factory work. | Produced item/design, quantity, BOM, routing, standard cost version, due date, location, priority, status. |
| Resource Planning | Capacity and booking controls for constrained work. | Resource, date/time, capacity slot, booking purpose, linked order or operation. |
| Shop Floor | Operation-level execution and WIP movement. | Operation, input/output status, material issue, completed quantity, scrap, rework. |
| Quality Control | Inspection evidence and release/hold decisions. | Template, sample size, measurements, defect category, disposition, inspected record. |
| Dispatch | Approved finished goods released to customer/location. | Customer, packed quantity, dispatch lines, delivery note, destination, carrier. |
| Billing | Invoice, deposit application, and payment follow-up. | Invoice customer, delivered lines, taxes, deposit applications, payment terms, allocation status. |
| Production Costing | Cost and variance review before or after closure. | Material, labor, machine, overhead, scrap, rework, WIP, finished goods, variance. |
| HR Payroll | Employee payout after production labour is approved. | Employee, pay period, production labour evidence, gross pay, deductions, net pay, payment batch. |
Production Planning And MRP
Use Production -> Operations -> Production Planning after confirmed demand is captured and before production orders are released.
Planning helps users:
- run MRP for a selected business unit, horizon, warehouse, or item
- review demand, material requirements, shortages, suggestions, and exceptions
- convert production-order suggestions into planned production orders
- open planning reports with the current run or row filters already applied
See Production Planning And MRP for the full workflow and report reference.
Source Demand And Release Gates
Production orders can be sourced from approved production quotations or sales orders. When that happens, the Production Orders workspace shows the source document and any linked engineering change so users can verify the handoff before release.
Quote-sourced orders should not be released without the corresponding approved engineering change unless an approved override is intentionally used. The release gate status makes that decision visible as pending, passed, blocked, or overridden.
Resource Operations
Production resource operations are exposed from Production -> Operations and use the shared Resource Capacity engine scoped to PRODUCTION resources.
Use them to:
- create capacity slots for work centers, machines, lines, tools, and labor pools
- reserve resources for production orders or operation-level work
- block capacity for maintenance, downtime, cleaning, setup, or unavailable shifts
- review utilization by resource, business unit, location, and date range
- detect bottlenecks before production is released or dispatched to the floor
- enforce overdue maintenance or calibration blockers before constrained work reaches the schedule
Labor Booking For Piece-Rate Work
When a garment operation is paid or measured by completed pieces, open the operation completion action and enter both Piece Quantity and Piece Rate. Pinkapple records the pair on the operation event and creates the actual labor cost as:
Piece Quantity x Piece Rate
Leave both fields blank when the operation uses the configured hourly labor rate. Entering only one field is rejected because a partial piece-rate booking cannot be reconciled. Piece-rate actual cost capture is tied to production operation completion; it does not replace payroll settlement, employee enrollment, statutory deductions, or historical payroll import.
For a school-uniform pilot, normalize the legacy worker ledger first, then map each row to a production operation, worker or labor pool, product/customer context, quantity, rate, date, and source reference before posting or reconciling it.
When the operation has multiple operators, book the labour per operator at operation completion. The operation line is the manufacturing milestone; the operator rows explain who earned the cost and how much should later be reviewed for payroll. Production should not mark the customer order fully closed until those labour bookings are either included in payroll or formally reconciled as not payable.
Production labour bookings are not employee payments. They become payroll earnings when HR generates the normal payroll run for the period. Use HR -> Operations -> Payroll Processing from the same active business unit context as the payroll actor, review the automatically collected production labour by employee and production order, then approve and pay through the HR/Payments flow. Do not create a separate production supplementary run.
The payroll run should remain in the actor's active business unit. Do not switch to a separate HR service, all-services context, or unrelated business unit just because the labour came from production. If the run appears under the wrong business unit or if the employees are missing from the detail drawer, stop and correct the payroll context before approval.
When operation completion is submitted from the standard Production Orders UI, the system attempts the configured production cost absorption posting for eligible completed work. A successful completion with a posting warning is not a reason to repeat the operation; fix the accounting blocker and retry Post Costs from the production order row. A clean completion and clean posting should leave no separate GL step for the user to remember.
Production labour costing and HR payroll should reconcile through a labour absorption clearing account. Production records the order cost; HR later records the employee payable and payment batch. If the same worker amount appears as a direct expense in both places without the clearing account being relieved, pause closeout and review the posting rules.
For the complete customer-order closeout, follow Production Order To Dispatch, Billing, And Payroll.
Scheduling And Dispatch
The Production Dispatch List combines the dispatch schedule, scheduling runs, assignments, exceptions, calendars, shifts, changeover rules, reschedule requests, and segment workflows. Use the page tabs to move between those views while keeping the production context and current tab reflected in the route.
Scheduling exceptions include missing resource type, missing resource, no capacity, capacity overload, slot blocked, maintenance blocked, calibration blocked, and downtime blocked. Treat maintenance and calibration blockers as release or scheduling stops until the underlying resource readiness record is corrected.
Quality Gates And Certificates
Production quality control opens the shared inspection workspace with production context. Users can work through inspection records, NCRs, CAPA, and supplier scorecards without creating a second production-only QC ledger.
For controlled finished goods, use production QC records linked to the production order, lot, batch, serial, or dispatch readiness reference. Approved evidence can feed Certificate of Analysis or Certificate of Conformance reporting when the customer or category requires formal proof.
For each production QC point:
| Step | User Action |
|---|---|
| 1 | Resolve the sampling plan for the item, operation, supplier, customer, category, or lot size. |
| 2 | Record the inspection with the selected sample size, accept number, reject number, and results. |
| 3 | Capture measurement values against the numeric specification limits where the template expects them. |
| 4 | Create an NCR or quality hold when the finding blocks release, dispatch, receipt, or acceptance. |
| 5 | Open CAPA when containment, root-cause review, corrective action, or preventive action is needed. |
| 6 | Release, rework, reject, downgrade, or certify only after the approved quality decision is recorded. |
Supplier quality scorecards use supplier-linked inspections, NCRs, and open CAPA backlog. Use them before reducing inspection levels, enabling skip-lot sampling, or accepting a supplier back from watch, probation, or blocked status.
Recall And Regulatory Traceability
Use the recall trace-back and trace-forward reports when a suspect material lot, batch, serial, container, license plate, or finished output needs investigation. The reports follow production genealogy through material issue, WIP, returns, output receipt, warehouse, and zone context.
For food and process manufacturing, include expiry bucket and regulatory trace profile filters where relevant. Trace rows show expiry status, food/process profile classification, NCR counts, and open quality blockers so users can identify whether an affected batch is traceable, expired, expiring soon, or still blocked by quality action.
Keep the downstream ownership clear during operations:
- Sales Orders, Procurement, Material Receipts, and Dispatch may open from Production context, but the structured document truth remains in shared Document Transactions
- stock issue, receipt, transfer, valuation, and availability remain owned by Inventory
- inspection pass/fail, defect, and evidence truth remain owned by Inspections
- receivable invoicing, customer deposits, and customer payment allocation remain owned by Billing
- money movement, settlement, and payout execution remain owned by Payments
- employee payroll and statutory remittance remain owned by HR Payroll
Operating Rules
- Do not release production until BOM, routing, materials, location, and quality setup are ready.
- Use material receipts and stock movements to keep inventory traceable.
- Use capacity slots and bookings when production work depends on constrained resources.
- Resolve maintenance and calibration blockers before forcing schedule or release decisions.
- Record partial completion, scrap, rework, and exceptions instead of forcing a clean completion.
- Use inspections to block or release output before dispatch where quality control applies.
- Use trace-back/trace-forward reports before clearing recall, expiry, or regulated batch investigations.
- Close production only after output, material usage, costing, operator labour, payroll handoff, and variance review are complete.
Do not create a second production-only commercial, stock, or QC ledger to explain these outcomes. Use the shared primitives and let Production provide only the manufacturing runtime context.