Skip to main content
GullySystem
Automotive

Stock Tracking and Alerts for Bus dealerships

Track physical bus chassis and complete vehicles by identity, allocation and custody.

Inventory Management

Does this function belong in your operation?

Use where the dealership physically holds or records the external custody of identified sale units.

A dealer-held unit is received, allocated, transferred, held or counted.

Two similar chassis in the yard can belong to different customer commitments. Once one leaves for a body builder, its identity and custody must remain traceable without appearing as available stock at both locations.

Bring the records the workflow depends on.

  • Chassis identity, specification and ownership reference
  • Current yard or external custodian and receiving evidence
  • Available, allocated and held states
  • Movement, count and authorised correction records

Outputs to check

  • Identified chassis and bus register
  • Allocation and external-custody history
  • Unreceived, held and count-difference list

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. Verify opening identities

    Match actual units to supplier and ownership references.

  2. 2. Record receipt

    Keep expected arrivals separate until physical receipt is checked.

  3. 3. Allocate the unit

    Link the chassis or bus to its accepted customer commitment.

  4. 4. Track custody movement

    Retain outward and receiving references for the yard, builder or other authorised holder.

  5. 5. Reconcile differences

    Investigate missing, duplicated or held units before correcting availability.

Who uses the module, and who approves?

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

Yard custodian

Checks identity and location at each receipt and release.

Sales coordinator

Reserves the correct unit and refers proposed substitutions for review.

Stock reviewer

Reconciles physical counts and external acknowledgements.

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 chassis is shown as available

Keep it outside received stock until actual evidence exists.

Builder return uses a different identity

Hold the discrepancy for reconciliation with the relevant owners.

Same unit appears in two yards

Review transfer acknowledgements instead of creating another vehicle.

Can this work independently?

A manually checked unit register is sufficient to start. Manufacturer feeds and builder exchanges need supported authorised access. Custody, ownership, technical readiness and customer delivery are separate facts; a stock movement does not establish all four.

Systems and records it connects with

  • Supplier receipts: identity and physical arrival.
  • Orders: accepted allocations and releases.
  • Builder records: outward custody and return acknowledgements.

Configure, test and introduce the workflow.

  • Count yard chassis and reconcile units held externally.
  • Test an expected arrival, duplicate identity and unmatched builder return.
  • Match trial availability to accepted orders before using it for sales commitments.

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 physical unit has one traceable identity and current custody state.
  • An external movement preserves the customer allocation without duplicating stock.
  • Held units are distinguishable from freely available supply.
Bus dealerships

How the business operates.

A school asks for a bus, but the proposal may cover a complete vehicle or a chassis with body work arranged separately. The dealership needs to identify the actual supply boundary before quoting or promising a handover. This proposed software scope follows new-bus enquiries through specification, accepted commercial terms, identified chassis allocation and delivery evidence. Where a body builder is involved, its instruction, custody and completion records stay distinct from the dealer’s sale. Technical suitability, operating permission and lender decisions remain with their responsible authorities.

Buyer and specification desk

Record the intended passenger use and the buyer’s requested configuration. A transport coordinator, school committee and legal purchasing entity can be different parties. Identify who advises on the requirement and who can accept the commercial proposal.

Chassis and body coordination

Keep the chosen chassis specification beside the body scope and responsible supplier. Distinguish factory-complete supply from a separate body arrangement. A chassis delivered to a builder has changed custody; it is not evidence that the customer received a finished bus.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Buyer organisation, purchasing authority and operational contact
  • Requested use, chassis specification and body-scope revision
  • Versioned chassis or complete-bus quotation with separate supplier boundaries
  • Accepted order, deposit evidence and identified chassis allocation

Operational bottlenecks to check

The committee compares different supply boundaries

One offer includes body work while another covers only a chassis. Keep included items and the seller responsible for each part explicit before comparing or accepting totals.

A chassis movement becomes a false delivery

The yard records an outward movement to a builder and sales closes the customer order. Keep builder custody and final customer receipt as distinct events.

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 purchase

    Identify the purchasing entity, decision contacts and intended use. Record whether the buyer wants a complete bus or a chassis with separately arranged work.

  2. 2. Confirm the proposed supply

    Retain the chosen specification and specialist review references. Assign unanswered body, equipment and documentation questions before presenting a final commercial version.

  3. 3. Accept and allocate

    Link the accepted proposal to a customer order. Allocate an identified chassis or bus only when available, keeping unallocated requirements and pending supplier acceptance visible. A requested delivery date remains separate from the coordinator’s readiness decision.

  4. 4. Track external custody

    Where applicable, record the builder’s accepted instruction and actual receipt of the chassis. Keep amendments, reported progress and return evidence linked to that same identity.

  5. 5. Review the completed supply

    Reconcile the unit and supplied scope against the order. Qualified parties determine technical readiness; document and funding owners record their own unresolved conditions.

  6. 6. Hand over and reconcile

    Record actual customer collection and outstanding obligations. Issue the appropriate dealer bill and allocate verified payments without treating handover as proof of settlement.

Industry reports to connect with

  • Enquiries awaiting a purchasing-authority or supply-boundary decision
  • Accepted orders with unallocated chassis identities
  • Chassis at external builders with unacknowledged movements
  • Body-scope amendments and unresolved readiness conditions

Questions before implementation.

When should bus dealerships consider stock tracking and alerts?

Use where the dealership physically holds or records the external custody of identified sale units. A dealer-held unit is received, allocated, transferred, held or counted.

What should we bring to the requirements discussion?

Bring anonymised examples of Chassis identity, specification and ownership reference; Current yard or external custodian and receiving evidence; Available, allocated and held states; Movement, count and authorised correction records. 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 bus chassis and complete vehicles by identity, allocation and custody. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The register does not certify body work, establish title transfer or approve vehicle operation.

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 physical unit has one traceable identity and current custody state. 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