Skip to main content
GullySystem
Automotive

Stock Tracking and Alerts for Car dealers

Track physical dealer vehicles by identity, location and availability state.

Inventory Management

Does this function belong in your operation?

Use when a dealer holds cars that must be individually located and assigned.

A dealer car is received, moved, allocated, held or physically counted.

Car stock needs one record for each physical vehicle. Model quantities are useful for planning, but a buyer receives a particular chassis with a particular variant, colour and yard position. Separate incoming expectations from received units and keep demonstration use, allocation and inspection holds visible. A transfer between yards changes location and custody; it must not create another car in the stock total.

Bring the records the workflow depends on.

  • Chassis or vehicle identification number and exact specification
  • Physical location, receipt and transfer evidence
  • Available, allocated, demo and inspection-held states
  • Confirmed order allocation and count-review rules

Outputs to check

  • Identified-car stock and yard-location register
  • Allocation, movement and hold history
  • Unreceived arrivals, count differences and stock-age review

Follow the stock tracking and alerts workflow.

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

  1. 1. Establish opening units

    Verify physical identity, specification, location and current state.

  2. 2. Record receipt or movement

    Link each actual unit to the source and receiving custody record.

  3. 3. Maintain allocation and holds

    Preserve customer assignment, demonstration use and inspection decisions.

  4. 4. Reconcile the yard

    Investigate missing, duplicate or mislocated identities before correction.

  5. 5. Review supply needs

    Compare available units and expected arrivals with commitments; supply decisions remain separately authorised.

Who uses the module, and who approves?

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

Yard custodian

Checks the vehicle identity at receipt and movement and reports physical differences.

Stock planner

Reviews available units, expected arrivals and open commitments before requesting supply.

Delivery coordinator

Confirms the unit chosen for handover and refers unresolved holds to the responsible reviewer.

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.

Expected car has not arrived

Keep it outside physically available stock until receipt is recorded.

Chassis entered twice

Hold the duplicate and reconcile identity against the physical car and source document.

Unit moved to another yard

Retain dispatch and receiving acknowledgement without counting both locations as holding the car.

Inspection hold discovered after allocation

Keep the affected buyer allocation visible while readiness and any replacement are reviewed.

Can this work independently?

Unit tracking can operate from manually checked receipts, counts and movements. Every allocation and transfer needs a stable vehicle identity. Manufacturer feed access is separately verified; an expected arrival is not physical stock. The stock register does not establish ownership transfer, technical readiness or customer delivery.

Systems and records it connects with

  • Supplier or manufacturer records: checked expected-arrival and actual receipt references.
  • Vehicle orders: active allocations and approved releases.
  • Yard and preparation records: movements, inspection holds and readiness decisions.

Configure, test and introduce the workflow.

  • Count chassis identities across yards and reconcile demo use and allocations.
  • Test an expected arrival, duplicate identity, transfer and post-allocation hold.
  • Compare trial available stock with physical units and pending commitments before routine planning.

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.

  • Each received car has one physical identity and current location.
  • Demo and held units remain separate from available sale stock.
  • A transfer preserves one vehicle balance and both custody references.
Car dealers

How the business operates.

A car dealership moves a buyer from model enquiry and test drive to an accepted commercial proposal, vehicle allocation and physical handover. The buyer’s requested variant is a specification; the chassis or vehicle identification number identifies the car actually supplied. Keep enquiry, booking payment, confirmed order, allocated unit and delivered vehicle as separate records. This profile centres on new-car retail, including documented exchange and finance handoffs. Used-car acquisition, repair operations and corporate fleet tenders require their own scope.

Sales and demonstration

Capture model, variant, transmission and usage requirements, assign a consultant and retain the next action. Test drives need an available demo, responsible employee and key-custody record.

Commercial and external documentation

Maintain quotations and approved buyer decisions. Track actual lender and registration references, responses and payment evidence. An internal status change does not create external approval.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Buyer enquiry, source, preferred specification, consultant and permitted follow-up
  • Demo vehicle, appointment, check outcome, key release and return
  • Versioned price proposal, optional items, exchange assessment and accepted terms
  • Booking reference, confirmed order and allocated chassis or vehicle identification number

Operational bottlenecks to check

One household has several enquiries

Preserve each buyer and requirement while linking related contacts. A shared phone number alone is insufficient evidence that two requested vehicles are the same sale.

A quoted colour is not an allocated car

Keep model-level availability and a physical chassis allocation separate. Yard transfers or rejected inspection findings must update the allocation before another delivery discussion.

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. Qualify the enquiry

    Record the requirement and buying stage. Link duplicate contacts without collapsing separate vehicle requests. Decide whether the next action is a visit, test drive, quotation or permitted later follow-up.

  2. 2. Arrange the demonstration

    Reserve the requested demo model and responsible staff. Record the operator’s required checks before key release, then retain return condition and customer feedback. Demo completion does not create a sales commitment.

  3. 3. Agree the commercial proposal

    Show the variant, included and optional items, confirmed charges and assumptions. Keep exchange and finance references separate. Retain the accepted version and unresolved conditions.

  4. 4. Confirm and allocate

    Record the booking’s status under the applicable terms, verified payment and order approval. Allocate an identified unit only when available. A substitution needs a recorded decision and any required customer acceptance.

  5. 5. Review delivery readiness

    Track inspection, accessories, documents, external approvals and payment conditions independently. A requested collection day remains a request until the responsible coordinator confirms the required readiness decisions.

  6. 6. Invoice and hand over

    Reconcile billing and confirmed receipts. Match the physical car to its allocation and documents. Record keys, collection and unfinished obligations with their owners.

Industry reports to connect with

  • Enquiries and overdue actions by consultant, source and model
  • Demo requests, completed drives and unavailable vehicle conflicts
  • Confirmed orders awaiting a physical unit or readiness decision
  • Vehicle age in stock, yard location, allocations and inspection holds

Questions before implementation.

When should car dealers consider stock tracking and alerts?

Use when a dealer holds cars that must be individually located and assigned. A dealer car is received, moved, allocated, held or physically counted.

What should we bring to the requirements discussion?

Bring anonymised examples of Chassis or vehicle identification number and exact specification; Physical location, receipt and transfer evidence; Available, allocated, demo and inspection-held states; Confirmed order allocation and count-review 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. Track physical dealer vehicles by identity, location and availability state. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Replenishment alerts are planning records, not manufacturer commitments. The dealer confirms vehicle condition, release authority and actual availability.

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. Each received car has one physical identity and current location. Use this check when reviewing the first working version.

Talk to us

Discuss stock tracking and alerts 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