Skip to main content
GullySystem
Manufacturing

Order Management for Sensor 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.

Orders arrive against a model code, quantity and range, including OEM custom builds. Lab capacity for the calibration range is checked first. Delivery dates follow element supply from the fab.

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.
Sensor manufacturers

How the business operates.

A pressure, temperature, proximity or gas sensor is bought for its accuracy. Customers rarely open the housing. They trust what the label and certificate say, and an auditor will ask to see what stands behind both. That trust rests on records made during calibration. Today they live on the test station or in an engineer’s folder.

Sensor models and variant codes

Hold each family with its valid ranges, outputs and connections, along with the cable lengths and labels that customers are allowed to choose. Sales picks only combinations that engineering has released. Surprises stop.

Sensing element lot control

Receive elements by lot with the readings taken on incoming samples, and issue them to builds in the order the stores should use them. A finished unit shows the element lot it carries.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Families and variant rules. Hold every family with its valid ranges, outputs, connections and cable lengths, so a custom OEM variant is released once by engineering and then quoted freely. Quotes stay inside released codes.
  • Sensing element lots. Receive elements by lot, record incoming readings against the datasheet limits and hold failing lots, so each build shows the exact lots it consumed. Lookups run both ways.
  • Bills of materials and builds. List elements, boards, housings, seals, potting compound and cable for each model, and let build orders issue the parts while recording the operator and the bench. Parts issue against the bill.
  • Calibration runs and coefficients. Store readings at every calibration point, the coefficients written to the unit and the chamber or pressure controller used, and route units outside limits to rework or scrap. Each run keeps its record.

Operational bottlenecks to check

Calibration data leaves with the engineer

Readings sit in a file on the calibration station. Two years after shipment a customer asks for a certificate, and the lab must find proof of what the bench measured on that day. The station has been replaced. The file is on a disk nobody can find.

Reference instruments fall out of date

The master gauge or reference thermometer has a calibration due date. Without a register, units are calibrated against an instrument whose own certificate has lapsed, and the work of a whole week has to be repeated from the first point.

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 variant check

    The buyer names a range, an output such as 4 to 20 mA and a process thread, then the model code is checked against released variants before quoting. An unbuilt combination stops here.

  2. 2. Element receipt and incoming test

    Sensing elements arrive in lots with supplier readings, incoming samples are measured against the datasheet, and a lot that fails is held. Nothing from it reaches the bench.

  3. 3. Assembly and sealing

    Elements are bonded to boards, housed in stainless bodies and then potted or laser welded, and operators log the adhesive or potting compound batch used with each build. Every build names its bench.

  4. 4. Calibration

    Units go into a temperature chamber or onto a pressure controller, readings at each point are stored, coefficients are written, and the master instrument is recorded against the run. Failures go to rework.

  5. 5. Final test and certificate

    Accuracy, hysteresis and ingress checks are done and attached to the serial number, then a certificate prints from the stored readings. A reprint matches the original.

  6. 6. Shipment and field feedback

    Units ship with labels and certificates, and later returns and drift reports are booked against the serial number and grouped by cause for the design team. Patterns show up.

Industry reports to connect with

  • Units calibrated by day, station and technician
  • Master gauges and thermometers due or overdue
  • Element lots with failing incoming readings
  • Hysteresis and ingress failures by model and cause

Questions before implementation.

When should sensor 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.

Related functions for sensor manufacturers.

    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