Skip to main content
GullySystem
Manufacturing

Product Management for Adhesive 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 grade is held with its pail, drum and cartridge sizes, viscosity range and data sheet. A hot melt and a water-based emulsion keep separate specifications. Quotes come from one list.

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

How the business operates.

Adhesives are judged by whether they hold. A carton maker wants a glue that sets at line speed, a footwear factory wants a bond that survives flexing, and a woodworker wants an open time that fits the press. Each need leads to a different formulation. None is interchangeable.

Formulations and recipes

Hold each grade’s recipe with revision history, scaled to the kettle size, and its allowed raw material substitutions.

Raw material lots

Record resin, polymer, solvent and additive lots with their incoming viscosity and solids, and link them to each batch.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Grades and formulations. Hold recipe revisions for every grade, with allowed substitutions of tackifier or plasticiser and quantities scaled to the kettle size.
  • Raw material lots. Record resin, polymer, solvent and additive lots with incoming viscosity and solids. Each lot links to every batch that drew from it.
  • Kettle batch records. Capture charging order, jacket temperature, dispersion blade speed, mixing time and the operator for each kettle batch.
  • Viscosity and solids. Save Brookfield viscosity, solids content and pH against the batch. Readings are compared with each grade’s limits before release.

Operational bottlenecks to check

Viscosity drifts between batches

The same recipe gives a thicker batch when a resin lot changes. Readings sit in a notebook. The pattern is never seen.

Bond tests are not tied to the batch

A peel strength result is written on a test strip. Weeks on, nobody can say which pail in the customer’s store it describes.

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. Order and plan

    A customer order, or a forecast for a repeat grade such as a case-sealing hot melt, opens a kettle batch. It carries the recipe revision and the quantity to make.

  2. 2. Weighing and charging

    Resins, tackifiers, plasticisers, solvents or water, fillers and additives are weighed in charging order, and each raw lot number is recorded as it goes into the jacketed kettle. Scale readings stay on file.

  3. 3. Mixing

    The operator notes jacket temperature, dispersion blade speed and mixing time, then a sample goes to the laboratory. The kettle waits.

  4. 4. Laboratory release

    Viscosity, solids, pH, ring and ball softening point and peel or lap shear results are saved. The batch is released, reworked or held.

  5. 5. Filling

    Pails, drums, IBC totes, tubes or cartridges are filled and checked on the scale, and a batch code and use-by date are printed on each. Short fills are caught at the scale.

  6. 6. Dispatch

    Orders are picked by remaining shelf life and ship with the technical data sheet revision and safety data sheet the customer approved. Paperwork matches.

Industry reports to connect with

  • Brookfield viscosity and solids by kettle batch and grade
  • Peel and lap shear results against customer limits
  • Resin and polymer lots used in a chosen batch
  • Pails, drums and cartridges filled by batch code

Questions before implementation.

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

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