Skip to main content
GullySystem
Manufacturing

Product Management for Specialty chemical manufacturers

Maintain the item definitions used by sales, purchasing and stock.

Inventory Management

Does this function belong in your operation?

Use when several business processes need the same product or service definitions.

An item, service code or variant is added or changed.

Every product holds its grades, pack sizes, data sheet revision and the customers who buy it. A new viscosity grade is added once. Technical sales staff quote from the current sheet only.

Bring the records the workflow depends on.

  • Item codes
  • Units and variants
  • Pricing and tax references

Outputs to check

  • Controlled item and variant catalogue
  • Unit and classification reference
  • Item-change approval history

Follow the product 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. Request the item

    Identify its business use and check for an existing equivalent.

  2. 2. Define attributes

    Set units, variants and required classifications.

  3. 3. Review settings

    Check price, tax and stock-related references with the responsible owners.

  4. 4. Approve use

    Release the item to permitted transactions.

  5. 5. Maintain history

    Control changes and retirement without rewriting earlier documents.

Who uses the module, and who approves?

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

Counter or sales staff

Finds the item by whatever they call it, and sees the rate and what is in stock.

Store and purchase

Adds new items with their units, rates and reorder levels before the first delivery arrives.

Owner

Controls who may change a rate. In most shops that is a very short list.

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.

Duplicate item discovered

Review linked transactions before merging or retiring a code.

Unit changes after use

Preserve historical quantities and define any conversion for future entries.

Item discontinued

Restrict new use under the agreed rule while retaining old orders and stock history.

Can this work independently?

The catalogue can exist independently, but sales, purchasing and stock must use its identifiers to share records. Prices and taxes may be maintained in separate controlled settings. Adding an item does not create opening stock or confirm that it is available to sell.

Systems and records it connects with

  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Purchase order management: Authorised supplier commitments and open line balances.
  • Barcodes and labels: Item-code mappings and verified printed-label values.

Configure, test and introduce the workflow.

  • We look at your sheet and counter software. You provide an export, and we report on duplicates and gaps.
  • A coding scheme and categories are proposed. You approve them before anything is loaded. Duplicates are merged with your staff. Each decision is logged for later reference.
  • A sample of items is loaded into a test copy. You check units, rates and tax codes. Billing and stores read from the new list. A short session for each team closes the step.

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.

  • Item codes are unique.
  • Units remain consistent across transactions.
  • Inactive items follow the agreed transaction rule.
Specialty chemical manufacturers

How the business operates.

Specialty chemicals are sold on what they do. One buyer wants a dispersant that keeps a pigment from settling. Another wants an additive that shortens a cure. The recipe behind that behaviour is the company’s real asset. Lose it and the product is gone.

Laboratory trials and formulations

Record each trial with its recipe, test results and customer feedback, and promote the approved one to a formulation version.

Scale-up and pilot batches

Link a trial to its pilot batch and then to every production batch that follows it, and compare viscosity, solids and performance results at each scale so that a drift appears early.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Customer enquiries and requirements. Log each enquiry with target properties, the end application and the customer’s own acceptance tests.
  • Laboratory trial register. Record trial recipes, bench results and customer feedback, then compare variants side by side. Nothing stays in a notebook.
  • Formulation versions. Hold approved recipes with revision history, an owner and the date each customer approved them.
  • Scale-up and pilot batches. Link a trial to its pilot and production batches, and compare yield, solids and viscosity across the bench, pilot and plant scales.

Operational bottlenecks to check

Trials and production recipes are disconnected

A chemist’s notebook holds the winning variant. The production master record is retyped by a supervisor, and a transcription slip changes the product.

Raw material variation passes unseen

A surfactant lot arrives from a new supplier. Its activity is slightly different. Nobody notes it.

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

    A customer problem is logged. It states the target properties, the application test the customer will run, and the contact who will judge the sample.

  2. 2. Laboratory trials

    Each trial variant is recorded with its recipe, bench viscosity and pH readings, and the customer’s feedback on the sample is attached beside them.

  3. 3. Approval and scale-up

    The approved trial becomes a numbered formulation version. A pilot batch comes first, and only then does the recipe move to full production.

  4. 4. Production

    The master batch record is followed step by step at the kettle. Raw lots, charge order, reaction temperatures, agitator hold times and in-process samples are written as they happen.

  5. 5. Release

    Viscosity, pH, solids, moisture by Karl Fischer and the customer’s own parameters are tested against the limits. The lot is released or held.

  6. 6. Shipment

    The certificate of analysis and the current data sheet are printed. The lot is then filled to pails, drums or IBCs and labelled with the batch number and hazard pictograms.

Industry reports to connect with

  • Trials open and their customer feedback
  • Formulation versions and approval dates
  • Pilot and production batches by product
  • Batches held or released by test result

Questions before implementation.

When should specialty chemical manufacturers consider product management?

Use when several business processes need the same product or service definitions. An item, service code or variant is added or changed.

What should we bring to the requirements discussion?

Bring anonymised examples of Item codes; Units and variants; Pricing and tax references. 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. Maintain the item definitions used by sales, purchasing and stock. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An item catalogue does not itself manage stock movements or fulfilment.

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. Item codes are unique. Use this check when reviewing the first working version.

Related functions for specialty chemical manufacturers.

    Talk to us

    Discuss product 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