Software marketplaceDEMOSOFT / SELECTION GUIDE
Choosing software for car parts, tyres and accessories
Compare AutoSoft, TireShopSoft, AutoGadgetSoft and AuCatalog API access by purpose, integrations, pricing and limitations.
Publisher: DemoSoft / FALCOSOFT ITS LTD · Updated:
Questions to clarify first
- Do you need a vehicle parts catalogue, a tyre shop or an accessories store?
- Will you integrate a separate API service into an existing shop?
- Who provides rights to catalogue data, fitments, images, prices and stock?
- Which payment and supplier integrations need production configuration?
Compare purpose and pricing
This guide uses DemoSoft’s current product descriptions. Prices exclude VAT; review the full details, demo and licence for your chosen product.
| Product | Purpose | Pricing and status |
|---|---|---|
| AutoSoftSoftware system | For parts retailers connecting vehicle navigation, product offers and customer orders in one workflow. |
|
| TireShopSoft — new tyres and Runflat shopSoftware system | A Bulgarian tyre shop platform for brand-new tyres, a Runflat selection, customer orders, mobile fitting appointments and store administration. EUR250 is the software package price. |
|
| AutoGadgetSoft — automotive accessories storeSoftware system | A standalone Bulgarian automotive accessories store with guest quick orders, a customer account and store administration. EUR250 is the one-site software package price. |
|
| AuCatalog · API access keyAPI service access | Prepaid access to the AuCatalog service through an individual API key for your shop, ERP or application. Access is sold for 6 or 12 months; the platform and source code remain with AuCatalog. |
|
Features, integrations and limits by product
AutoSoft
Modules
- Vehicle catalogue — select a make, model and configuration.
- Products — categories, part numbers, media and demo supplier offers.
- Commerce and administration — cart, orders and a separate admin workspace.
Integrations
- The shop backend requests AuCatalog data; its API key stays on the server.
- A supplier must authorise catalogue data, media, prices and stock. Fitment and offer freshness require separate validation.
- A live deployment needs store details, tax rules, payments, shipping and webhook processing.
- Includes a server-side TypeScript adapter for the TecDoc API by TecAlliance: manufacturers, models, vehicles, exact part/OE/EAN number search and article details. A separate contract, API key and Provider ID are required, followed by live API validation and mapping to internal storefront IDs.
Scope and limitations
An isolated AutoShazam copy with example offers. Production payment, courier and supplier credentials are not included. The TecDoc component is implemented but not configured or connected to live data. No TecAlliance subscription, data, images, prices or stock are included. The demo storefront continues to use its example catalogue.
Details, demo and terms →TireShopSoft — new tyres and Runflat shop
Modules
- Responsive dark grey/orange Bulgarian storefront;14 different new-tyre models with original product photographs and six source-listed Runflat variants.
- Size, season, brand, vehicle-class, XL, Runflat, price and stock filters; favourites, three-product comparison and galleries.
- Separate catalogue identities and supplier offers; server-side carts, transactional stock reservations and order price snapshots.
- Stripe Checkout and signed webhooks; online cards, courier COD and payment on collection.
- Speedy, Econt and Pigeon Express HTTP adapters: offices, quotes, labels and tracking, using your own contract and credentials.
- Mobile fitting: illustrative equipped van, address/date/time booking, pricing, capacity checks, confirmation and cancellation.
- Operational independent admin; customers, orders, activity, prices, stock, tariffs, draft products, PNG galleries and atomic CSV offer import.
- Runflat explanation with compatibility, TPMS and post-puncture limitations.
Integrations
- Python3.11+,SQLite,HTTPS reverse proxy and private storage; source,documentation,tests and deployment examples included.
- Bootstrap your own operator; no universal embedded password.
- Configure your own Stripe account and signed webhook; a return URL never marks an order paid.
- Courier consoles use provider-native schemas and your sender,office/city IDs,service,weight and COD instructions.
- Pigeon requires the provider-issued API origin,key and secret; the official schema omits server origins.
- Checkout delivery uses a store tariff; carrier contract quotes are separate. Link labels and reconcile COD payments in administration.
Scope and limitations
Public demo performs no real charges,shipments or visits. Prices,stock and suppliers are fixtures; source-listed variants are not a live feed. No automatic VIN fitment,SMS provider,carrier/Stripe contract,fiscal invoicing,password-reset email or automated refunds. No live carrier account verification. Third-party marks and photography are separate from the software licence.
Details, demo and terms →AutoGadgetSoft — automotive accessories store
Modules
- Responsive dark grey/red Bulgarian UI; six categories, thirteen products and genuine manufacturer product photographs.
- Bulbs, filters, oils, mirrors, cables and car gadgets; category/brand/price/stock filters, SKU search, three-product comparison and favourites.
- Guest quick ordering directly from a product; preserves an existing cart. Standard cart checkout also permits guests.
- Customer order history/status, tracking number, payment and cancellation of new unpaid orders.
- Stripe Checkout and signed webhooks; courier COD and payment on collection.
- Speedy, Econt and Pigeon Express HTTP adapters for offices, quotes, labels and tracking.
- Independent admin: product metadata, PNG galleries, stock, prices, atomic offer CSV imports, customers, guest orders, activity and configuration.
- Isolated public demo sessions and read-only public administration; independent installations support authenticated operators.
Integrations
- Python3.11+,SQLite,HTTPS reverse proxy; source,documentation,tests and deployment examples included.
- Bootstrap your own operator and configure catalogue,offers,stock,tariffs and store policies.
- Use your own Stripe account and signed webhook. A browser return never marks an order paid.
- Couriers require your own contracts and provider-native schemas; Pigeon supplies its API origin.
- Checkout delivery is a configurable store tariff. Contract quotes and label creation are operator actions.
Scope and limitations
Demo stock and prices; no live supplier feed. No automatic VIN/TecDoc fitment,fiscal invoices,SMS/email service,automated refunds or password reset. Guest orders are available in their protected24-hour session and transfer to the account upon login. Domain,hosting,provider accounts and live account verification are not included. Photography and trademarks remain separate from the code licence.
Details, demo and terms →AuCatalog · API access key
Modules
- Vehicles — makes, models, generations and configurations for navigation.
- Parts — articles, categories, brands, OEM references, specifications and fitments.
- Offers and provenance — demo prices, stock, expiry and source classification.
- API access — Bearer authentication, operation scopes, datasets and rate limits.
Integrations
- Use backend-to-backend HTTPS calls to /api/v1/ with a dedicated Bearer key; never embed it in frontend code.
- Follow the OpenAPI contract, handle pagination and 401/403/429 responses, and cache according to data validity.
- Map vehicle and article IDs; refresh price, stock and expiry before sale. VIN identification alone does not prove part fitment.
Scope and limitations
The public explorer uses the existing isolated AutoSoft AuCatalog through a restricted server-side facade. External providers, VIN and research operations are disabled. Inter Cars and Laximo are planned. A server-side TecDoc adapter is implemented for TecAlliance, but licensed API configuration, live validation and storefront ID mapping remain required; the provider is not active.
Details, demo and terms →Before deployment
Confirm the selected licence, installation environment, external services and required data rights. Test the workflows that matter to your project. See the FAQ or contact [email protected] for available options and the installation service.