Skip to main content
GullySystem
Manufacturing

Sales Returns and Credit Notes for Plastic component manufacturers

Record customer returns and link their financial and stock effects.

Sales and Distribution

Does this function belong in your operation?

Use when supplied goods or billed amounts can require returns or credit adjustments.

A customer requests a return or credit.

Rejected housings returned by an equipment builder are booked against the original invoice with the defect noted. The quality engineer sees which mould produced them. Credit notes follow once the return is inspected.

Bring the records the workflow depends on.

  • Original invoice
  • Returned quantities and reasons
  • Acceptance and stock-disposition rules

Outputs to check

  • Authorised return and inspection record
  • Stock-disposition statement
  • Credit or refund handoff

Follow the sales returns and credit notes workflow.

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

  1. 1. Register the request

    Identify the original sale, quantity and stated reason.

  2. 2. Authorise the return

    Apply the approved commercial and eligibility rules.

  3. 3. Receive and inspect

    Count returned goods and record their condition.

  4. 4. Decide disposition

    Separate saleable stock, repair, rejection and other approved outcomes.

  5. 5. Issue the adjustment

    Pass accepted quantities to credit or refund processing and reconcile the original balance.

Who uses the module, and who approves?

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

Counter staff

Finds the original sale, records the return reason and follows the authorised acceptance process.

Storekeeper

Counts what came back and says plainly what is fit to sell again.

Accounts assistant

Raises the credit note and sets it against the bill, so the ledger and the warehouse tell the same story.

Owner

Approves returns above a value, and reads the monthly reasons.

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.

Return exceeds sold quantity

Hold the excess for investigation before stock or credit posting.

Goods damaged on return

Record condition and approved disposition separately from saleable stock.

Invoice already settled

Route the approved credit to an account balance or refund process without duplicating payment.

Can this work independently?

Returns need the original sale or an approved exception reference. Inventory records accepted quantities and condition; accounting issues credits and manages refunds. A return request does not prove goods arrived, and receiving goods does not automatically authorise a full financial refund.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Stock: Item-location quantities and authorised stock movements.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Quality control: Inspection results and authorised hold or release decisions.

Configure, test and introduce the workflow.

  • We trace a return from gate to ledger. You show recent cases, and a written flow is sent back.
  • Reasons and time limits are agreed. You approve the list used in the screens. The note is matched to your invoice series and tax details. Accounts proof a sample.
  • Saleable and damaged bins are set up. The storekeeper tries both paths. Returns start here on an agreed day. The owner receives a monthly count.

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.

  • Credits do not exceed authorised returns.
  • Damaged stock is distinguished from saleable stock.
  • Balances reconcile with the original invoice.
Plastic component manufacturers

How the business operates.

Industrial buyers do not order parts. They order part numbers at a stated drawing revision, released through call-off schedules that the buyer reissues, moving quantities, before the last pallet has cleared your dock. When revision C replaces revision B, the old stock in the racks becomes either a problem or a sale.

Part and revision register

Hold part numbers with drawing revision, resin grade, mould and packing specification, and block a superseded revision from release so the racks hold nothing unshippable.

Customer schedule intake

Load each weekly release and compare it with the previous one, so the planner sees every line that moved and nobody builds against a stale copy of the call-off.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Component quotations. Price a part from resin weight, cycle time, press tonnage, assembly steps and returnable packing, and keep each quote revision beside the drawing revision it priced. Old quotes stay readable.
  • Part and revision register. Hold each part number with drawing revision, resin grade, mould, packing specification and cut-in date, and count stock by revision rather than by part alone. A superseded revision cannot be released.
  • Customer schedule intake. Load each weekly release, compare it with the last, and show what moved in quantity and date for every part and customer before anyone touches the press schedule. The diff is the first screen.
  • Tooling ownership list. List each mould with its owner, rack, cavity count, shot count and last maintenance, so a customer’s tooling audit is answered from the list, not the racks. Audits stop being a walk.

Operational bottlenecks to check

Revisions overlap in the racks

Revision B parts sit beside revision C parts on the same shelf, and the customer’s line stops when a pallet of the wrong one arrives at the receiving bay. Cartons carry no revision label.

Schedules change faster than plans

A weekly release replaces the last one, and planning against an old copy builds the wrong quantity of PA66 housings while leaving the right one unmade.

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. Drawing and quotation

    The buyer’s drawing revision, tool ownership terms, resin grade and volume are recorded, and the quote prices moulding at cycle time before adding each assembly step and returnable packing. No price without a revision.

  2. 2. Tooling and first article

    The mould enters the register under its owner, with cavity count and shot counter, and measured samples with the customer’s approval are stored before volume release. Volume waits for sign-off.

  3. 3. Schedule intake

    Each weekly release is loaded and compared with the last, so the planner sees which quantities rose, fell or moved date for every part number. Changes are listed, not hunted for.

  4. 4. Moulding and cells

    Runs are planned against the schedule and the press that holds the mould, then parts move through degating, trimming and insert fitting with counts logged at each step. Every step reports a number.

  5. 5. Kitting and dispatch

    Parts are packed into trays to the customer’s count and labelled with part number and revision, and a delivery note travels with the load recording the tray count out. Trays are counted out.

  6. 6. Returns and corrective action

    A customer return is linked to its run, mould and cavity, the cause is written down, and the corrective action stays open until the customer confirms it. Closure needs the buyer’s reply.

Industry reports to connect with

  • Customer call-off changes by part number and week
  • Stock by part and drawing revision
  • Returns by customer, part, mould, cavity and cause
  • First-article approvals with sign-off dates

Questions before implementation.

When should plastic component manufacturers consider sales returns and credit notes?

Use when supplied goods or billed amounts can require returns or credit adjustments. A customer requests a return or credit.

What should we bring to the requirements discussion?

Bring anonymised examples of Original invoice; Returned quantities and reasons; Acceptance and stock-disposition 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 customer returns and link their financial and stock effects. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Consumer obligations, tax treatment and refund policy require your adviser-approved rules.

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. Credits do not exceed authorised returns. Use this check when reviewing the first working version.

Talk to us

Discuss sales returns and credit notes 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