Skip to main content
GullySystem
Manufacturing

Order Management for PCB manufacturers

Track a confirmed order through fulfilment and billing.

CRM

Does this function belong in your operation?

Use when sales, operations and billing share confirmed orders.

A customer confirms goods or work.

A buyer’s order for two hundred panels is split into lots by delivery date. Every lot shows its stage in the process. Part shipments leave the balance open for sales to see.

Bring the records the workflow depends on.

  • Order lines
  • Commercial terms
  • Fulfilment rules

Outputs to check

  • Confirmed order and revision record
  • Outstanding fulfilment list
  • Delivered and billed reconciliation

Follow the order management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Capture confirmation

    Record accepted quantities, price and terms.

  2. 2. Check release conditions

    Review credit, approval and any stock or capacity requirements.

  3. 3. Authorise fulfilment

    Pass the confirmed lines to dispatch, production or service delivery.

  4. 4. Record partial progress

    Compare accepted fulfilment evidence with the remaining order balance.

  5. 5. Reconcile and close

    Match billing and approved cancellations before closing the commitment.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Sales executive

Takes the order and confirms the delivery date. Tells the buyer when half has gone.

Storekeeper

Picks against the order. Records short quantity. Closes the line only when it is out of the gate.

Accounts assistant

Bills the dispatched quantity and keeps the advance adjusted against the right order.

Owner

Sees orders pending beyond their promised date, and which customer is waiting longest.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Partial delivery

Record the supplied portion and retain the balance against its original line.

Customer cancels remaining work

Obtain approval and close only the unfulfilled portion.

Agreed price changes

Version the order and review whether invoices or advances need separate adjustment.

Can this work independently?

Orders can be entered from an accepted customer instruction without CRM. Stock, production, service delivery and invoicing connect through order-line references. Each owns its execution record; an order status should reflect their confirmed outcomes rather than assume delivery from a planned date.

Systems and records it connects with

  • Quote and proposal management: Commercial proposal versions and acceptance details.
  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • Walk us through an order from call to payment. A note shows the steps and the documents.
  • Decide which changes need approval. A test order can then be taken, with your own staff at the keys. Share orders still pending. The trial import shows quantities dispatched and pending for the storekeeper to check.
  • Sales and the store team practise a part delivery. A note for the counter follows. New orders go through the system from the date you agree. Changes from the opening week are reviewed together. Habits settle quickly.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Partial fulfilment leaves correct balances.
  • Term changes follow approval.
  • Billing follows approved quantities.
PCB manufacturers

How the business operates.

A bare board order starts as a set of files and ends as a stack of boards in a vacuum bag. In between, a panel passes a dozen wet and dry steps, and every step has its own scrap. One late revision can sink a lot.

Order and file revision register

Hold the buyer’s Gerber set, fabrication note and revision, so CAM and the floor never image from an outdated pack.

Engineering query tracker

Log each CAM question, send it to the buyer, record the answer and release the lot only when all queries are closed.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and quotations. Price boards from layer count, size, panel utilisation, finish and quantity bands, with every revision of a quotation kept.
  • File revision register. Attach the Gerber set, drill file and fabrication note to the order with a revision letter, and show the floor only the released set.
  • Engineering queries. Raise a CAM question, send it to the buyer, record the answer and block the lot until the query is closed.
  • Stack-up and panel plans. Hold the laminate, prepreg and copper weight of each build, with boards per panel and panel size.

Operational bottlenecks to check

The wrong Gerber revision gets imaged

The buyer resends files after CAM has started, and the film is made from the old set while the new revision waits in an inbox that the floor never opens. The error shows only on the electrical test.

Engineering queries wait in email

A clearance question to the buyer sits unanswered while the lot waits for tooling. The planner cannot tell which orders are blocked on a reply.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and quotation

    A buyer sends files and a fabrication note. The estimator checks layer count, size, finish and quantity, and prices from panel utilisation.

  2. 2. CAM review

    CAM checks clearances and drill data, raises engineering queries and lays out the panel. The order is released only after the buyer’s answers.

  3. 3. Lot creation

    A lot opens with the file revision, stack-up and a traveller by process step. Laminate and prepreg are issued against it.

  4. 4. Process steps

    Imaging, etch, lamination, drilling, plating, mask, legend, finish and routing are each logged with quantity in, quantity out and scrap reason.

  5. 5. Test and inspection

    Open and short test results are saved by board. Final inspection checks dimensions, finish and visual defects.

  6. 6. Packing and shipment

    Boards are counted, bagged and labelled with the date code. The certificate of conformance, test report and packing list are issued.

Industry reports to connect with

  • Yield by process step, by week and by board type
  • Orders waiting on engineering queries
  • Scrap reasons for drilling, plating and etching
  • Lots affected by a given bath change or press load

Questions before implementation.

When should pcb manufacturers consider order management?

Use when sales, operations and billing share confirmed orders. A customer confirms goods or work.

What should we bring to the requirements discussion?

Bring anonymised examples of Order lines; Commercial terms; Fulfilment rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Track a confirmed order through fulfilment and billing. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Stock, production and carrier connections need agreed scope.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Partial fulfilment leaves correct balances. Use this check when reviewing the first working version.

Talk to us

Discuss order management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements