Skip to main content
GullySystem
Manufacturing

Goods Receipt (GRN) for Uniform manufacturers

Record what physically arrives against a supplier order.

Procurement

Does this function belong in your operation?

Use when purchased physical goods need quantity and acceptance checks on arrival.

Purchased goods arrive at a receiving location.

A truck of fabric rolls is checked against the mill’s delivery note by metres and shade lot. Short rolls and flawed lengths are noted before the driver leaves. The merchandiser then knows what cutting can start.

Bring the records the workflow depends on.

  • Purchase order
  • Delivery note
  • Acceptance and storage rules

Outputs to check

  • Numbered receipt and inspection record
  • Accepted and rejected quantity statement
  • Purchase-order balance and bill-match inputs

Follow the goods receipt (grn) workflow.

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

  1. 1. Identify the delivery

    Match the supplier and delivery note to the order or approved exception.

  2. 2. Count the goods

    Record actual quantities separately from the supplier's stated quantities.

  3. 3. Inspect and classify

    Distinguish accepted, held, damaged and rejected goods.

  4. 4. Post accepted receipt

    Update the appropriate location only for the authorised quantity.

  5. 5. Handover for matching

    Pass receipt evidence to purchasing and accounts while leaving undelivered balances open.

Who uses the module, and who approves?

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

Storekeeper

Counts, enters and keeps the delivery note. The entry made at the dock is what moves stock.

Accounts assistant

Passes bills only against what was received, and holds the rest for purchase to settle.

Purchase executive

Sees which orders are part-delivered and which vendor keeps sending short.

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.

Excess delivery

Record the excess separately and obtain the purchasing decision before accepting it.

Damage at unloading

Capture condition and hold or reject the affected quantity.

Receipt without PO

Route the exception for authorisation and establish a valid purchasing reference before bill approval.

Can this work independently?

Goods receipt needs item and supplier references; a purchase order is preferred or an explicitly approved unplanned receipt is required. Stock posting, quality release and invoice approval are separate handoffs. Receiving a delivery note does not prove that the stated goods were counted or accepted.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Stock: Item-location quantities and authorised stock movements.
  • Vendor bills: Supplier invoice lines and authorised posting status.
  • Quality control: Inspection results and authorised hold or release decisions.

Configure, test and introduce the workflow.

  • We watch how material comes in and who signs for it. You describe the problems met at the gate. A short list of what needs recording returns to you.
  • Open purchase orders and the item list are brought in. The purchase team checks a sample for accuracy. The storekeeper enters real deliveries on a trial screen next to the paper register. Gaps in the form are found and fixed.
  • Hold rules, batch numbers and weighbridge entries are set where they apply. You approve which items need them. Storekeepers and the accounts desk practise on phones and screens. The paper register stops on an agreed date.

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.

  • Receipt quantities link to the purchase order.
  • Rejected goods remain distinct from accepted stock.
  • Partial deliveries leave the correct balance due.
Uniform manufacturers

How the business operates.

A uniform order starts with people, not with a style. The buyer supplies a list of wearers and sizes, and the maker turns it into a cutting plan for shirts, trousers, skirts, tunics or jackets in the approved fabric and colour.

Wearer lists and size runs

Load the buyer’s wearer list, check sizes against the size chart and turn it into a size ratio for cutting.

Approved sample register

File each signed sample with measurements, trims, shade card and photographs, and a repeat order can begin from the identical garment.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Wearer lists and size runs. Import the buyer’s wearer list, check each size against the size chart, and build the size ratio the cutting room will lay.
  • Approved sample register. Hold each signed sample with its measurements, trims, shade card and photographs, and flag the version a repeat order should follow.
  • Fabric and trims intake. Receive fabric rolls and trims against the supplier’s delivery note, record shade and shrinkage checks, and hold a roll until it passes.
  • Cutting plan and bundles. Plan lays by size ratio, record lay length and pieces cut, and tag bundles so each one can be traced to its fabric roll.

Operational bottlenecks to check

Wearer lists change after cutting

A school sends corrected sizes once the fabric is already cut. Part of the order is then made twice, and nobody notes which bundles were replaced.

The approved sample is not on file

The signed sample hangs on a rail or sits in a cupboard. Months later a repeat order is stitched to a memory of it, and the buyer sees a different collar.

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 sample

    The buyer’s garment, fabric and colour are quoted. A sample is made, corrected and signed, and the signed version is filed.

  2. 2. Wearer list

    The list of wearers and sizes is loaded, checked against the size chart and converted into a size ratio for cutting.

  3. 3. Fabric and cutting

    Rolls are received, shade checked and laid by ratio. Cut pieces are bundled and tagged with their roll.

  4. 4. Stitching and checking

    Bundles go through operations on the line. Checkers pass, return or reject, and rework goes back to the operator.

  5. 5. Logo and finishing

    Embroidery, badges and name tapes are added, garments pressed, measured against the sample and tagged.

  6. 6. Packing and delivery

    Sets are bagged by wearer, cartons listed by class or department, and the delivery note matches the order.

Industry reports to connect with

  • Pieces cut, stitched and packed by order
  • Rework and rejection by operation
  • Fabric used against fabric planned
  • Orders pending by buyer and delivery date

Questions before implementation.

When should uniform manufacturers consider goods receipt (grn)?

Use when purchased physical goods need quantity and acceptance checks on arrival. Purchased goods arrive at a receiving location.

What should we bring to the requirements discussion?

Bring anonymised examples of Purchase order; Delivery note; Acceptance and storage 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. Record what physically arrives against a supplier order. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

A goods receipt does not replace specialist inspection or approval of the supplier's invoice.

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. Receipt quantities link to the purchase order. Use this check when reviewing the first working version.

Talk to us

Discuss goods receipt (grn) 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