Skip to main content
GullySystem
Automotive

Price Lists and Schemes for Battery dealers

Apply dated price lists and promotional rules to eligible transactions.

Sales and Distribution

Does this function belong in your operation?

Use when prices vary by customer group, channel, quantity or promotion.

A price or commercial offer changes.

Distributor price lists and brand schemes set the selling rate by model. Quarterly targets show how far the shop is from the next slab. Rebates follow the Ah rating.

Bring the records the workflow depends on.

  • Item prices
  • Customer eligibility
  • Validity and combination rules

Outputs to check

  • Effective-dated pricing register
  • Offer eligibility and application record
  • Discount-exception report

Follow the price lists and schemes workflow.

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

  1. 1. Create the price basis

    Record items, buyer groups and effective dates.

  2. 2. Define offer rules

    Set eligibility, limits and whether offers combine.

  3. 3. Approve publication

    Review exceptions and release the authorised version.

  4. 4. Apply to transactions

    Select the correct terms during quoting or billing.

  5. 5. Review overrides

    Retain manual discounts and preserve historical transaction prices.

Who uses the module, and who approves?

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

Billing clerk

Checks the selected customer terms and raises any requested override through the discount approval rule.

Sales executive

Quotes from the list the customer is on, and knows what the running scheme allows a promise of.

Owner

Sets the lists, approves what goes below them, and sees the discount given this month against last.

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.

Two offers overlap

Apply the defined precedence or require review instead of stacking them by accident.

Customer group changes

Use the agreed transaction date and preserve earlier billed prices.

Manual discount requested

Route the exception under the approval limit and record the final authorised rate.

Can this work independently?

Pricing can be maintained independently, but quoting or billing must use the approved selection rules for consistent application. Customer groups and item codes provide eligibility. The price module does not establish stock availability, contractual acceptance or whether a promotion is legally permitted.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Dealer portal: Partner identities, submitted orders and permitted account information.

Configure, test and introduce the workflow.

  • Hand over price sheets, scheme letters and the discount habits of the counter. A note groups them into lists.
  • Decide who sits on which list and how far each role may go. Bills that pick the right rate come back. Try them. Staff raise sample bills from several lists. Corrections return as an adjusted set of lists.
  • Billing clerks and sales staff practise approvals. A reference sheet for the counter follows. The next offer is entered with its dates. A review after it ends checks what each party paid.

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.

  • Expired offers stop applying.
  • Eligibility rules select the intended buyers.
  • Old transactions retain their original rates.
Battery dealers

How the business operates.

A serial number and a date code are stamped on the lid of each battery that leaves the counter. Months later it returns with a dead cell, and the claim stands or falls on a record the dealer must find in seconds.

Battery stock by brand, model and serial

Hold stock by brand, model, ampere-hour rating and chemistry, with serial and date code keyed in on receipt. The counter then hands out the oldest unit first.

Sale and warranty record

Tie every sale to a serial and a customer, with the free-replacement window and the pro-rata period read from the brand’s terms. A claim opens from the invoice, never from a lost card.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Battery stock by brand and serial. Hold stock by brand, model, ampere-hour rating and chemistry, with serial and date code on every unit, and scans at receipt and sale keep the shelf count honest. No stock-taking guesswork.
  • Date codes and stock ageing. List units by manufacture date and flag the ones nearing the age at which charge is lost, so the counter picks the oldest unit first. Shelf life is protected.
  • Counter billing with exchange rebate. Quote two rates for each model, with or without an old core. The rebate prints on the bill, and the serial is added to the invoice line so the warranty record starts at the counter.
  • Sale and warranty record. Tie every serial to a buyer and a date, and read the free-replacement and pro-rata periods from the brand’s terms, so a claim opens straight from the invoice. Proof is already filed.

Operational bottlenecks to check

Serials sit only on the warranty card

The customer loses the card. The dealer cannot show which 150Ah tubular inverter battery went out, or on what date, and the brand rejects the claim.

Old batteries are not counted

Exchange rebates are given at the counter, yet the count of scrap cores received, load-tested, held and sold to the smelter’s buyer is nobody’s figure.

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. Receive stock

    Stock arrives against the supplier’s delivery note. Serial and date code are keyed or scanned, and each unit goes on the shelf as a record the counter can find by rating and make.

  2. 2. Quote and bill

    The counter quotes a rate with and without an old core, raises the bill and ties the serial to the buyer’s name and phone. The warranty period starts from that day.

  3. 3. Take back the old core

    The returned battery is logged with brand, rating, terminal condition and weight. The rebate shows on the bill, and the core goes into the exchange register to wait for its load test.

  4. 4. Handle a warranty case

    The bench records open-circuit voltage and the drop test result, tags the unit and sends it to the service centre, and the customer is told where the battery stands. No guessing.

  5. 5. Collect trade dues

    Garage and electrician accounts show the balance by age. A reminder fires ahead of the credit ceiling, receipts are posted against bills, and old dues stay visible on the list for the collector.

  6. 6. Claim brand schemes

    Purchases and sales are set against each brand’s slab, and the claim form is prepared from the record when the period closes. Targets are checked as the month runs.

Industry reports to connect with

  • Stock by brand, model, serial and manufacture date
  • Batteries sold by serial, buyer and warranty end date
  • Cores received, tested, held and sold, with rebate allowed
  • Warranty cases by stage, brand and age

Questions before implementation.

When should battery dealers consider price lists and schemes?

Use when prices vary by customer group, channel, quantity or promotion. A price or commercial offer changes.

What should we bring to the requirements discussion?

Bring anonymised examples of Item prices; Customer eligibility; Validity and combination 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. Apply dated price lists and promotional rules to eligible transactions. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Commercial policy and permitted promotional terms must be approved by your business.

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. Expired offers stop applying. Use this check when reviewing the first working version.

Talk to us

Discuss price lists and schemes 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