Skip to main content
GullySystem
Automotive

Stock Tracking and Alerts for Electric car dealerships

Keep physically held electric cars and equipment distinguishable by identity, location and allocation status.

Inventory Management

Does this function belong in your operation?

For dealerships controlling physical stock; an online manufacturer listing alone is not dealer-held inventory.

A car or separately held item is received, moved, allocated, released or physically counted.

Count the cars and charging equipment the dealership physically controls, separating demonstrators, allocated vehicles and units held for review. A model-level quantity does not identify the car committed to a buyer. Retain vehicle identity, location and the responsible preparation reference. Equipment compatibility is a qualified decision outside the stock balance. A battery programme changes commercial records, but it does not create a separate loose battery in the showroom's physical stock.

Bring the records the workflow depends on.

  • Actual vehicle identities, variant references and custody locations
  • Demonstrator, held-unit and customer-allocation records
  • Counted separate equipment with ownership and approved item references

Outputs to check

  • Identified vehicle and separate equipment register
  • Reservation, hold and custody movement history
  • Count differences and supply requirements

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 actual holdings

    Count identified cars and separately held equipment. Record custody and ownership so a customer-owned or demonstrator vehicle is not mistaken for unallocated new stock.

  2. 2. Record receipt and movement

    Retain source and destination evidence. Keep a shipment notice separate from the dealership’s actual receipt.

  3. 3. Link a reservation

    Associate the allocated vehicle with the accepted order under the authorised decision. Do not promise a buyer any car simply because the model balance is positive.

  4. 4. Review holds and differences

    Keep units awaiting authorised preparation decisions distinct from available stock. Investigate missing equipment or identity differences before making a reviewed adjustment.

  5. 5. Refer a shortage

    Send a specific vehicle or equipment requirement to the procurement owner. The alert does not accept a substitute or approve a manufacturer allocation.

Who uses the module, and who approves?

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

Stock custodian

Maintains identities, locations and physical movement evidence.

Preparation owner

Supplies the authorised review status without allowing a stock balance to certify readiness.

Allocation reviewer

Connects available units to actual accepted orders.

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.

Demonstrator counted as ordinary stock

Correct its classification and retain the use history for the authorised sale decision.

Battery plan mistaken for loose inventory

Keep commercial battery terms with the order; record a separate physical battery only if it is actually held as an item.

Equipment appears compatible

Require the approved product reference and qualified decision rather than substituting by appearance.

Vehicle is announced but not received

Retain expected supply separately until physical receipt is recorded.

Can this work independently?

The register can begin with approved counts and entered movements. Manufacturer feeds require verified access and still need custody reconciliation. Qualified staff or providers own technical preparation and equipment suitability; the supplier owns its allocation response. Stock thresholds are prompts for review.

Systems and records it connects with

  • Manufacturer dispatch and actual receiving evidence.
  • Accepted order and authorised allocation decision.
  • Preparation reference and actual handover movement.

Configure, test and introduce the workflow.

  • Count sale cars, demonstrators and held units separately.
  • Test a received vehicle with missing equipment and an announced shipment.
  • Check that a changed allocation preserves identity and accepted specification.

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 reserved car retains an actual identity.
  • Held and demonstrator units remain separate from ordinary availability.
  • Physical counts do not include imaginary loose batteries from finance arrangements.
Electric car dealerships

How the business operates.

An electric-car buyer agrees on a vehicle but still needs a decision about apartment charging and a clear explanation of the battery agreement. The showroom must keep these questions open even after a booking payment arrives. This requirements model covers new battery-electric cars sold through a dealership's actual retail arrangements. It connects buyer discussions, the accepted vehicle and battery terms, identified stock, external charging referrals and the physical handover. A battery supplied with the car, separately financed or provided under another documented arrangement needs the corresponding contract references; the programme name alone does not establish ownership. These are proposed business records, not verified GullySystem features.

Buyer advice and demonstrations

Record the intended use, selected model and unresolved questions about charging access. A corporate buyer, driver and payer can be different parties. Preserve what the adviser referred to the manufacturer or qualified charging provider instead of inventing an answer during a demonstration.

Commercial and battery terms

Keep the exact vehicle variant beside the accepted battery supply or finance arrangement. Identify each contracting party and any recurring obligation described in the actual documents. A vehicle price comparison must not conceal a separate battery obligation or imply that all programmes are leases.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Buyer, intended driver, payer and consented contact details
  • Selected vehicle variant and source product-information revision
  • Demonstration vehicle identity and recorded outcome
  • Battery supply, finance or usage agreement with provider and accepted version

Operational bottlenecks to check

A battery programme is described as a simple discount

The buyer accepts a headline vehicle amount without the separate obligation. Preserve the actual programme document, provider and buyer decision so later staff can explain what was agreed.

Charging referral is mistaken for installation

The buyer expects a working home charger because the showroom sent a request. Track referral, survey response and provider completion evidence separately, without letting the dealer record certify electrical work.

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. Understand the purchase

    Record who will buy and drive the car, the intended use and unresolved charging questions. Keep an information enquiry separate from a requested demonstration or an accepted sale.

  2. 2. Retain the demonstration outcome

    Identify the car used and the buyer feedback. Route unanswered technical questions to the proper owner; a drive does not prove the buyer will achieve a particular range.

  3. 3. Agree the commercial package

    Version the vehicle configuration and battery terms alongside equipment and accessories. Identify which obligations belong to the dealer and which require another provider agreement.

  4. 4. Allocate the actual unit

    Link an available vehicle only after the allocation decision. Check a changed unit against the accepted specification and preserve any buyer-approved amendment.

  5. 5. Resolve handover dependencies

    Review preparation evidence, buyer details and external responses under the actual sale terms. Keep an open charging-site referral visible even if another part of the order is ready.

  6. 6. Deliver and reconcile

    Record the vehicle, supplied items and recipient at handover. Retain any agreed outstanding item and its owner; reconcile the dealer bill independently of battery-provider or installer accounts.

Industry reports to connect with

  • Buyer questions awaiting manufacturer or charging-provider response
  • Accepted packages awaiting battery-agreement confirmation
  • Vehicles allocated, held for preparation or used as demonstrators
  • Orders with unresolved external dependencies by responsible party

Questions before implementation.

When should electric car dealerships consider stock tracking and alerts?

For dealerships controlling physical stock; an online manufacturer listing alone is not dealer-held inventory. A car or separately held item is received, moved, allocated, released or physically counted.

What should we bring to the requirements discussion?

Bring anonymised examples of Actual vehicle identities, variant references and custody locations; Demonstrator, held-unit and customer-allocation records; Counted separate equipment with ownership and approved item references. 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. Keep physically held electric cars and equipment distinguishable by identity, location and allocation status. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Stock software does not assess battery health, perform charging or establish electrical compatibility. Vehicle custody does not prove customer acceptance.

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 reserved car retains an actual identity. 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