Skip to main content
GullySystem
Automotive

Order Management for Electric scooter dealers

Track the accepted scooter package from original booking through actual unit allocation and complete handover records.

CRM

Does this function belong in your operation?

For local scooter retail or fulfilment arrangements with explicit seller authority and identifiable stock.

The purchaser confirms the package under the actual seller’s booking and sale process.

Match the original booking to the accepted scooter package and the party authorised to buy it. The rider, payer and recipient can differ. Track the identified unit and supplied charger, with removable packs only where the model actually uses them. Missing equipment and unconfirmed optional services remain separate open items. Preserve the actual seller's approval for changes rather than assuming the local counter can rewrite a manufacturer booking or purchaser identity.

Bring the records the workflow depends on.

  • Original booking, actual seller and accepted package revision
  • Purchaser, payer and authorised recipient
  • Identified scooter, supplied equipment and external-response references

Outputs to check

  • Accepted scooter package and identified allocation
  • Equipment shortages and external decision list
  • Actual recipient and handover record with open balances

Follow the order management workflow.

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

  1. 1. Confirm the retail commitment

    Match the original booking to the accepted variant and purchaser. Distinguish a local dealer sale from fulfilment of another entity’s order.

  2. 2. Check the allocated scooter

    Retain actual identity and preparation evidence from the authorised owner. A colour match does not prove the unit carries the accepted configuration.

  3. 3. Reconcile the supplied package

    Check the charger, removable packs where applicable and accessories. Record item-level shortages without marking the whole package physically complete.

  4. 4. Review external and optional items

    Keep registration responses, finance decisions and optional-plan acknowledgement separate. A completed local checklist cannot create the provider’s approval or activation.

  5. 5. Record the actual handover

    Identify the recipient and items supplied. Preserve any agreed open accessory or provider action, then reconcile the sale and booking references without closing those balances.

Who uses the module, and who approves?

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

Retail order coordinator

Maintains the original booking, accepted revision and seller authority.

Store and preparation owner

Provides actual unit, equipment and authorised readiness references.

Delivery coordinator

Records recipient and complete or outstanding package lines.

Accounts owner

Checks money records independently of physical fulfilment.

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.

Customer asks for a different scooter at collection

Review specification, seller approval and affected documents before replacing the allocation.

Removable pack or charger is missing

Keep the accepted line outstanding and obtain the authorised handover decision; do not substitute an unverified item.

Another person arrives to collect

Verify the actual purchaser’s authorised recipient through the seller’s process.

Optional service remains unconfirmed

Keep its provider acknowledgement open after physical delivery and name the follow-up owner.

The buyer requests cancellation

Verify who can request the change under the actual seller's process. Preserve the original booker and payer, then record the seller decision and any authorised unit release. Refund review and separate optional-provider commitments remain open until their own decisions are recorded.

Can this work independently?

Orders can start from entered accepted documents and original booking references. Stock, preparation, external authority responses and payment each provide their own evidence. Manufacturer connections require permission and verified support; order status does not grant the local dealer authority to change outside records. Customer acceptance does not establish manufacturer or supplier acceptance, physical availability or a confirmed unit allocation.

Systems and records it connects with

  • Accepted estimate and original seller booking.
  • Physical scooter, pack and charger records where applicable.
  • Actual handover, invoice reference and optional-provider response.

Configure, test and introduce the workflow.

  • Trace an in-store sale and a brand-booked scooter fulfilled locally.
  • Test a changed recipient, missing charger and replacement allocation. Include a cancellation request with an unresolved refund decision.
  • Confirm an open optional-plan enquiry survives recorded vehicle delivery.

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.

  • The supplied unit matches the accepted version or an approved revision.
  • Rider, purchaser and recipient are recorded separately where they differ.
  • Vehicle handover cannot close an undelivered item or unconfirmed optional service.
Electric scooter dealers

How the business operates.

A scooter buyer books through a brand website, a family member pays the token, and the local counter is asked to deliver a different colour with another battery option. The dealer needs the original reference and the accepted revision before treating those requests as one settled sale. This scope covers new electric-scooter retail through the business's actual manufacturer or retail-partner arrangements. It follows rider questions, variant and pack choices, physical scooter and accessory custody, the correct selling entity and handover. Removable packs or a separate battery plan are recorded only for models actually supplied that way. The proposed workflow does not run a battery-swapping network or claim installed GullySystem capability.

Counter enquiries and test rides

Keep the intended rider, purchaser and person making contact distinct. Record which model the rider tried and questions needing a product specialist. A family enquiry or online token does not settle the owner details, permitted road use or final package.

Variant and package confirmation

Identify the scooter variant, colour, supplied pack configuration and charger. Retain accessory and optional service-plan choices separately. When a model offers a battery usage arrangement, record the actual provider terms rather than presenting it as an ordinary included battery.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Brand booking reference, collection channel and verified payment evidence
  • Intended rider, purchaser, payer and authorised recipient
  • Variant, colour, pack configuration and accepted revision
  • Battery-plan provider and agreement reference where applicable

Operational bottlenecks to check

The online booker is not the purchaser

A relative’s contact appears on the booking while another person is meant to own the scooter. Resolve the correct identities through the actual seller’s process before billing; do not overwrite the payment trail.

Same colour, different pack or charger

The counter substitutes a visually similar scooter or charger and loses the accepted specification. Preserve variant and equipment references and obtain the relevant technical and buyer decisions.

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. Connect the counter enquiry

    Find the original brand booking or earlier visit without merging different riders or purchases. Confirm the contact’s role and record the question still preventing a decision.

  2. 2. Record the model experience

    Identify the test scooter and feedback. Refer compatibility, technical or permitted-use questions to the appropriate authority rather than promising that another variant behaves identically.

  3. 3. Agree the exact package

    Record colour, variant, supplied battery arrangement, charger and selected extras. Retain any new revision and the purchaser’s decision before allocation.

  4. 4. Match physical items

    Check the actual scooter and included equipment against the accepted package. Record an absent charger, missing pack reference or held unit separately; a carton count alone cannot prove a complete customer supply.

  5. 5. Complete the retail handoff

    Check the selling entity and applicable external responses. Record the actual recipient and supplied items, preserving outstanding optional accessories or account queries under the agreed terms.

  6. 6. Reconcile money and follow-up

    Match the original booking collection and later receipts without crediting the same token twice. Send unresolved charging, warranty or account questions to their actual provider with the accepted package reference.

Industry reports to connect with

  • Enquiries awaiting rider, purchaser or original-booking clarification
  • Variant or battery-plan revisions awaiting purchaser acceptance
  • Scooters held, available or allocated by actual identity
  • Incomplete charger, pack or accessory supply by order

Questions before implementation.

When should electric scooter dealers consider order management?

For local scooter retail or fulfilment arrangements with explicit seller authority and identifiable stock. The purchaser confirms the package under the actual seller’s booking and sale process.

What should we bring to the requirements discussion?

Bring anonymised examples of Original booking, actual seller and accepted package revision; Purchaser, payer and authorised recipient; Identified scooter, supplied equipment and external-response 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. Track the accepted scooter package from original booking through actual unit allocation and complete handover records. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

No workshop repair, battery swapping, automatic registration or connected-vehicle activation is performed by this order record.

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. The supplied unit matches the accepted version or an approved revision. Use this check when reviewing the first working version.

Talk to us

Discuss order management 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