Connect the showroom journey
A showroom sale passes through several records: an enquiry, a booking or advance, an invoice, payment and delivery. ABK Books provides connected workflows for these steps so the office can review the customer and vehicle history together. The system also includes quotations and follow-up work.
- Customer enquiries, bookings and quotations.
- Sales invoices, receipts and delivery records.
- Customer and scooter timelines.
Keep stock and after-sales work organised
The showroom needs to distinguish serialised scooters from quantity-based parts. ABK Books supports stock receipts, supplier records, stock counts and service workflows, including estimates, parts use and warranty-related records. Warranty terms come from the business rather than an invented software promise.
- Scooter and parts inventory records.
- Supplier bills, payments and purchase history.
- Service, repair and warranty workflows.
Review business records with the right access
The workspace includes expense handling, daily closing and accounting reports, with individual owner and staff accounts. Reports and statutory calculations still require business review. Contact Narvyn to discuss the intended showroom workflow and integration requirements; the implementation is not advertised as a universal, fully certified accounting package.
- Owner and staff access appropriate to the role.
- Expenses, money records and business reporting.
- A guided review of the required configuration and handover.
Questions, answered
Is ABK Books the same as PGonTrack?
No. ABK Books is an EV showroom implementation; PGonTrack is for paying guest accommodation.
Can another showroom use the same system?
Discuss your stock, sales, service and accounting requirements with Narvyn. Reuse and customisation depend on the agreed scope.
Does the software create warranty promises?
No. Warranty terms and business details must be supplied and approved by the business.
What should we confirm before an implementation?
Discuss availability and required scope. A similar implementation requires its own scope and quote. Bring your role list, example workflows, existing systems and migration needs. Use sample or redacted records for evaluation. Confirm hosting, support, integrations and handover in the written scope.