Skip to main content
GullySystem
Manufacturing

Business solutions for Personal care product manufacturers

Explore software for work such as “Private-label and contract orders from brand owners”. Review each business function below, including when it fits and what to check before implementation.

Personal care product manufacturers

How the business operates.

You buy surfactants, emollients, preservatives, fragrance oils, laminated tubes, pump dispensers and printed mono cartons, make bulk in a kettle batch, and fill it into packs. You sell through distributors and marketplaces, and some brand owners hand you their own formulas.

Ingredient and fragrance stock by lot

Receive surfactants, bases, colours and fragrance oils against a purchase order, with the supplier lot noted. Each issue to a batch ties to a work order, so use of every lot can be traced later.

Formulation and bulk batch record

Keep each formulation as a bill of materials with its batch size. Record quantity issued against quantity expected for every kettle batch, and hold the batch until a person clears the pH and viscosity readings.

Filling and packing stages

Record filled, rejected and reworked packs at filling, capping, induction sealing, labelling and cartoning, with operator and machine on each job card. Leftover tubes, pumps and cartons are counted when the job closes.

Packing component stock

Hold bottles, laminated tubes, pump dispensers, sachet film and printed cartons by artwork version, and show shortage against the jobs already released to the line.

Contract jobs for brand owners

Take a job order carrying the brand owner’s formula, pack and artwork revision, then dispatch against it. A separate view for each brand owner is built around the production software.

Batch-wise stock and returns

Hold finished stock by batch and expiry date, and log each return by batch and reason. This is not part of the production software as standard, so it is a separate build.

Stability test record

New creams and shampoos are kept at set temperatures and checked for colour, smell and separation. The record holds the batch, the check dates and the result. Quality staff fix the shelf life from it.

Retention sample register

One filled pack from every batch is stored on a shelf for later checks. The register lists the batch, the shelf position and the discard date. Complaints are compared with the kept sample.

Label artwork approval

Soap wrappers and shampoo labels list ingredients, net content and usage warnings. The approval record holds the artwork version and who signed it. Only approved versions go to print.

Customer complaint log

Customers report rashes, leaking bottles or a changed smell. The log ties each report to a batch, a product and the handler. Quality staff open an investigation from it.

The records that hold the operation together.

  • Approved formulation and bulk-batch reference
  • Ingredient lots and actual issues
  • Container, closure, label and artwork revision
  • Filling, packing, rejection and release records
  • Finished-batch dispatch, retained sample and complaint reference

Operational bottlenecks to check

Bulk yield and filled count disagree

Bulk made in the vessel, packs off the filling line and leftover bulk in the drum are measured on different sheets, so loss is guessed. The gap between kettle and carton is never explained.

Packing components run out mid-batch

Printed cartons, tubes and pumps carry artwork versions, and the wrong revision is found at the line with the shipper already half packed. Filling stops until the right stock is hunted down in the store.

A complaint cannot be tied to its batch

The batch record, the ingredient lots and the retention sample sit in three places. A distributor’s complaint about colour change or a leaking cap takes days to answer.

Contract jobs for other brands blur together

Each brand owner has a separate formula, pack and artwork, yet the files share one folder. A mix-up between two brands of shampoo is a real risk, and nobody sees it until a carton is opened.

Returns carry no batch detail

Distributors and marketplaces return packs with no batch code noted, so the cause is never traced to a mixing vessel or filling line. Credit notes are raised blind.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Agree the product and pack

    Record the formulation, pack size, artwork and brand-owner approval relevant to the order.

  2. 2. Make and identify the bulk batch

    Issue accepted ingredient lots and record the plant observations and actual yield required by the process owner.

  3. 3. Release and fill

    Quality authorises the bulk for filling. Record the containers, closures and artwork used, along with filled units, rejects and unused components.

  4. 4. Check the finished batch

    Attach the finished-pack checks and retained-sample reference. Keep held stock separate until the responsible person releases it.

  5. 5. Dispatch and investigate returns

    Identify the batch sent against each brand or customer order. Link returns and complaints to the batch and its original ingredients and pack materials.

Roles and responsibility boundaries.

Formulation owner and production supervisor

Controls the approved formulation and records bulk-batch issues, observations, yield and transfer to filling.

Quality and packing teams

Quality records the approved checks and release decision. Packing controls container and artwork versions, filled units, rejects and unused components.

Brand account, warehouse and accounts teams

The brand contact confirms the job specification. Warehouse and accounts reconcile released batches, dispatch, returns and the customer invoice.

Reports your managers need.

  • Bulk yield and filling reconciliation
  • Packing-component shortages by artwork version
  • Held and released finished batches
  • Complaints and returns by batch and reason

Connections to scope

  • Accounting: purchase, contract-job and dispatch documents
  • Quality files: results, retained samples and release decisions
  • Artwork repository: approved label and carton versions

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Separate formulas from artwork

Define independent approval and version control for the formulation and each printed packing component.

Trial a complete batch

Reconcile ingredients, bulk transfer, filled packs, rejects and unused components. Include a held batch and an artwork revision.

Train brand and plant hand-offs

Agree which records the brand contact, production staff, quality team and warehouse own before introducing live jobs.

Limitations to settle before implementation

  • Qualified product and quality personnel determine formulation, safety, stability and release requirements.
  • Brand-owner portals, expiry tracking and complaint workflows must be scoped separately where the selected product lacks them.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Private-label and contract orders from brand owners
  • Loan-licence arrangements with small brands
  • Hotel and hospitality amenity supply
  • Distributor-owned labels for a state or region
  • Salon and spa professional ranges
  • Export enquiries for bulk or finished packs
  • Repeat orders from buyers already trialled
  • New formula development for founders with an idea
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

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