Skip to main content
GullySystem
Manufacturing

Bill of Materials for API manufacturers

Define the materials and quantities needed for a manufactured item.

Manufacturing

Does this function belong in your operation?

Use when output quantities depend on a repeatable material or component list.

A product or production recipe is created or revised.

A stage lists starting materials, reagents and solvents with their quantity for each kilogram of output. A revision to the route creates a new version. Old routes remain readable.

Bring the records the workflow depends on.

  • Finished-item codes
  • Component quantities and units
  • Revision and waste rules

Outputs to check

  • Approved material and subassembly list
  • Versioned material cost basis
  • Quantity-exploded requirement sheet

Follow the bill of materials workflow.

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

  1. 1. Define the output

    Identify the finished item, production quantity and unit.

  2. 2. List components

    Record materials, subassemblies and quantity conversions.

  3. 3. Review allowances

    Approve waste factors and permitted substitutes.

  4. 4. Release a version

    Retain the approved definition and its effective use.

  5. 5. Calculate requirements

    Expand the selected version for a planned quantity and pass shortages to planning or purchasing.

Who uses the module, and who approves?

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

Estimator

Defines the material quantities and approved version used to cost a finished item or quotation.

Production in-charge

Sees what a job needs before it is released to the floor.

Storekeeper

Issues against the list. Anything beyond it is asked for in writing.

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.

Component unavailable

Use only an approved substitute and retain its effect on cost and specification.

Design revised after release

Keep existing jobs on their approved version unless a controlled change is authorised.

Unit conversion inconsistent

Resolve the conversion before calculating requirements or issuing material.

Can this work independently?

A bill of materials can be maintained independently for costing and planning. Stock, purchasing and work orders use its approved version when connected. It does not reserve materials or schedule machines by itself, and a rate-based material total excludes labour or overhead unless separately defined.

Systems and records it connects with

  • Production planning: Demand, planned quantities and resource or material constraints.
  • Work orders: Released production jobs, material issues and output records.
  • Purchase orders: Authorised supplier commitments and open line balances.
  • Stock: Item-location quantities and authorised stock movements.

Configure, test and introduce the workflow.

  • You show a few finished items and describe how they are made. You get a written note on how the parent items and sub-assemblies will be laid out. Begin with a few products.
  • You supply item names, units and wastage habits from your sheets. A trial import comes back for you to correct before anything is relied on. Corrections come cheaply here. Recent purchase rates are connected to the lines. A costed list for a few products is laid beside your own working for comparison.
  • The estimator and the storekeeper explode a batch on the trial. You hear what is missing, and the layout is changed. Gaps surface early. New quotations start from the list. The team is shown how to save a version and how to mark alternates.

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.

  • Component units are consistent.
  • Production uses the approved version.
  • Revisions preserve the earlier material definition.
API manufacturers

How the business operates.

An API plant makes a molecule in stages. Starting materials become intermediates, intermediates become crude product, and crude product is purified, dried, milled and packed. At every stage a sample is tested, and a stage that fails its specification can send material back for rework, reprocessing or rejection, each of which must be written down. Every step leaves a record.

Route and stage master

Hold each product’s synthesis route as stages with inputs, solvents, equipment and in-process test points.

Batch manufacturing records

Record charges, temperatures, hold times, yields and sample draws for each stage, with a reviewer’s sign-off.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Starting materials and suppliers. Receive materials with supplier lot, quarantine status and sampling records, and keep approved supplier lists.
  • Route and stage master. Define each synthesis route as stages with inputs, solvents, equipment and test points, with revisions under change control.
  • Batch manufacturing records. Record charges, parameters, hold times, yields and sample draws for each stage and each reviewer’s sign-off.
  • Intermediate lot genealogy. Link final lots to their intermediates and starting materials, including reprocessed and recovered material.

Operational bottlenecks to check

Intermediates lose their lineage

A final lot is built from three intermediate lots, and a reprocessed lot is blended in. The chain from final lot back to starting material is rebuilt from folders each time a customer asks.

Deviations sit in a separate file

A deviation raised during drying is tracked in a register that is not tied to the batch. Release goes ahead without anyone checking if it is closed. The gap is found later.

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. Starting material receipt

    Materials arrive against a purchase order, are sampled and are held until released by quality staff.

  2. 2. Stage charge and reaction

    Charges, temperatures, pressures and hold times are logged against the stage and the reactor used.

  3. 3. Isolation and drying

    Filtration, centrifuging and drying are recorded with yields and samples drawn.

  4. 4. Test and review

    Results are posted against the specification. The batch record is reviewed with its deviations before the next stage or release.

  5. 5. Mill, blend and pack

    The final powder is milled, blended and packed in sealed drums, each with a recorded seal number.

  6. 6. Release and dispatch

    The lot is released, a certificate is produced and the load is shipped with the retest date visible.

Industry reports to connect with

  • Batches by stage and product
  • Yield by stage across campaigns
  • Open deviations by age and stage
  • Intermediate lots and the final lots they fed

Questions before implementation.

When should api manufacturers consider bill of materials?

Use when output quantities depend on a repeatable material or component list. A product or production recipe is created or revised.

What should we bring to the requirements discussion?

Bring anonymised examples of Finished-item codes; Component quantities and units; Revision and waste 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. Define the materials and quantities needed for a manufactured item. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Use only for operations that make, assemble or formulate physical goods; ordinary service delivery needs a different workflow.

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. Component units are consistent. Use this check when reviewing the first working version.

Talk to us

Discuss bill of materials 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