Dealer Management System Integration in Australia: What Connecting Your DMS Actually Takes

Of the six vendors with a confirmed or claimed Australian presence, only two publish anything concrete about an API, and only one publishes readable documentation. The table below records what each vendor states on its own site as at July 2026, not what a salesperson might tell you. | Product | Serves Australia | Motorcycle or powersports focus | Public API | Public developer docs | Access model | |---|---|---|---|---|---| | Titan DMS (Queensland) | Yes, dedicated Australian site and integrations page | Yes, Motorcycle named as a served industry | Yes, advertises over 150 API endpoints, real-time and bi-directional | No open portal found. Site references standardised APIs, pre-built endpoints and test databases | Open API with around 80 named integration partners. No published fees or certification detail | | Pentana Solutions (eraPower) | Yes, reported as the Australian market leader | Not evidenced. Site language is automotive dealerships | Not published. Describes uni or bi-directional interfaces tailored to a needs analysis | No | Gated Integrated Partner Program with a dedicated partner manager and data security requirements. No fees published | | Auto-IT | Yes, reported second in the Australian market | Not specifically. Automotive, trucking, construction and agriculture | Not established by this research | Not found | Reported as integrating with nearly every OEM. Integration model not researched | | Revolution DMS (Parramatta, NSW) | Yes, Australian and New Zealand phone lines listed | Yes, positions itself as the industry standard for motorcycle dealerships | Not mentioned anywhere on its motorcycle page | No | Not published. The only integration referenced is its own Appraisals app inside the Revolution showroom module | | Blackpurl | Yes, Australian and New Zealand, with an Australian support line | Yes, built for powersports including motorcycles and jetskis | No. Site describes an API as upcoming for Blackpurl 2 | No | Pre-built integration catalogue only. The Shopify integration needs the Professional or Professional Plus package plus an additional cost | | Keyloop | Not confirmed by this research | Not evidenced. Automotive retail | Yes, more than 30 API products | Yes, at its public developer portal, no registration wall encountered | Documented security review process. No fees published | Two absences are worth stating carefully. We found no evidence that Lightspeed DMS, CDK Global, Reynolds and Reynolds, Ideal Computer Systems or Autologica serve Australian dealers, but this research did not run a dedicated Australian presence search per vendor. That is absence of evidence, not evidence of absence. Ask the vendor.

If you run a motorcycle dealership in Australia, the vendor that publishes the most about integration and names your industry is Titan DMS. Titan is Queensland-based, lists Motorcycle as a served industry alongside Automotive, Agriculture, Construction and Truck, and publicly advertises over 150 API endpoints with around 80 named integration partners including Carsales, Cox Automotive, Infomedia and Autograb. Blackpurl is the other product built for your category. It is powersports-first, covering motorcycles, jetskis and bicycles, runs an Australian support line and maintains a dedicated Harley-Davidson page for Australia and New Zealand. Its site still describes an easy API as upcoming for Blackpurl 2, so the honest position today is that Blackpurl does not publish a public API. What it does publish is a pre-built integration catalogue, and that catalogue is unusually specific. Revolution DMS is the awkward one. It positions itself as the industry standard for Australian motorcycle dealerships, and its motorcycle page mentions no API, no integrations and no e-commerce connection anywhere. That is an observation about what the vendor chooses to publish, not proof that no integration path exists. Plenty of vendors hold that material behind a partner conversation. It does mean that if you are on Revolution and you are planning a build, the first task is a written answer from the vendor rather than a page you can read. There is a structural clue about how fragmented parts operations really are. Blackpurl's own parts integration list spans HD-Net, HLSM, PartSmart, Snap-On EPC, Turn 14 Distribution, KTM North America, Husqvarna, GASGAS and Kayo. A DMS needing nine or more separate parts connectors is itself the evidence that supplier catalogues do not consolidate on their own.

Keyloop runs a genuine public developer portal with more than 30 API products, and you can read the documentation without hitting a registration wall. The published surface covers customers, vehicle inventory, payments, service appointments, parts ordering and event subscriptions. Keyloop states a customer base of more than 20,000 retailers, 80 OEMs and operations in more than 90 countries. That matters because it removes the excuse. When a vendor says a public API surface cannot be documented openly in this category for security or competitive reasons, one of the largest vendors in the category has already done it. Access is still governed, with a documented security review process, but the shape of what is available is public before you sign anything. Keyloop also publishes the caveat that most vendors leave you to discover during a build. Its own documentation states that not all endpoints, properties within an endpoint, or parameters within an endpoint are available or relevant for every dealer management system. Read that as the warning it is. Even inside one vendor's API programme, coverage varies by which DMS product sits underneath, so a documented endpoint is not the same as an endpoint that returns your data. This research could not confirm whether Keyloop serves Australian dealers. Its developer portal language references Europe, the Middle East, Africa and Asia. Treat Keyloop here as the documentation benchmark to hold your own vendor against, not necessarily as an option on your shortlist.

In Australian DMS, the API usually exists and the cost of using it appears nowhere a dealer can read. That gap is the actual project risk, not the technical work. No vendor in this research publishes the price of API or integration access. Not Titan, not Pentana, not Keyloop, not Revolution, and not Blackpurl beyond the phrase "an additional cost" attached to its Shopify integration. Pentana publishes the process but not the terms. Its Integrated Partner Program is described in three steps: understand your business model and requirements, assess the opportunity, then if successful integrate you into the partner programme. Partners get a dedicated partner manager and must meet all requirements for data security. Below that, nothing is published: no fee schedule, no certification checklist, no timeline. Titan markets its API as open and without restriction or lock-in, which reads well. Its own buyer guidance also tells dealers to understand any costs and restrictions that may be associated with these services. Those two statements sit oddly together. The most defensible reading is that Titan is acknowledging costs exist somewhere in the category, and this research could not resolve whether Titan itself charges. So the only honest advice is unglamorous. Ask the vendor directly, in writing, before you scope anything. Then price the delay as well as the fee, because partner approval processes in this category are slow, gated on a commercial assessment of your business model, and can be withdrawn. An integration whose access can be revoked is a different asset from one that cannot.

There is a documented reason the pricing vacuum persists, and it is not administrative. On 1 April 2017, in a DealerRefresh dealer forum thread about DMS API integration charges, participant Mark A Hoffman noted that vendors fear publicly criticising fee structures because of possible removal from certified vendor programmes or delays to their applications. That is a chilling effect, and it explains the shape of the information you can find. The people who know what integration access costs are the software vendors paying for it, and those vendors need to stay inside the certification programmes that set the price. Complaining in public risks the access. So the numbers stay in private contracts, and dealers researching a build find marketing pages instead of a rate card. The same 2017 thread does contain concrete figures, and they need three labels before anyone uses them. They are American, they are in US dollars, and they are from 2017. One dealer reported Lightspeed charging a setup fee of 2,000 US dollars per location plus 175 US dollars a month per location to maintain the API, which across four locations came to 8,000 US dollars in setup and 700 US dollars a month. Another reported a Reynolds integration fee rising to 465 US dollars a month for a third-party scheduling tool. We are deliberately not converting those to Australian dollars. They are nine-year-old American prices from a forum, quoted here to show that per-location integration fees are a real commercial model in this category. They are not a guide to what an Australian vendor will quote you, and no Australian DMS publishes integration pricing at all.

The United States has litigated DMS data access at scale, and Australia has not. Authenticom, a third-party data integrator, sued CDK Global and Reynolds and Reynolds alleging the two vendors conspired to cut it off from dealer data that it accessed using login credentials the dealers themselves had provided. The case ran as Authenticom, Inc. v. CDK Global, LLC and was later consolidated into In re Dealer Management Systems Antitrust Litigation. The settlements were large. CDK Global settled for US$600 million (about A$916 million at July 2026 rates) in January 2025 with a class of 244 software vendors, covering integrations purchased back to 2013, on an allegation that CDK restricted access to data and levied hundreds of millions of dollars in overcharges. A separate CDK class settlement in September 2024 was US$100 million (about A$153 million), and Reynolds and Reynolds settled at US$29.5 million (about A$45 million). CDK settled without admitting wrongdoing. Read that as history from another market, not as a precedent you can point at. Those figures describe two vendors we could not establish serve Australian dealers, under a statute that does not apply here, decided in courts with no authority over an Australian contract. The practical takeaway is narrower and still useful. Credential-based third-party integration, where a dealer hands its own DMS login to a data integrator, was precisely the model those vendors moved against. If an Australian integrator proposes that arrangement to you today, the American history is the reason to read your DMS agreement first.

Australia has no DMS data-access litigation or ACCC action that this research could find. What it does have is an adjacent scheme that is regularly and incorrectly cited as if it covered DMS vendors. The Motor Vehicle Service and Repair Information Sharing Scheme became mandatory on 1 July 2022, arising from recommendations in the ACCC's 2017 New Car Retailing Industry market study. The ACCC is the regulator and AASRA, the Australian Automotive Service and Repair Authority, is the appointed scheme adviser running day-to-day operations. The obligations are specific. A manufacturer that shares service and repair information with any authorised supplier must supply the same information to all Australian repairers and registered training organisations that request it. It must charge no more than fair market value. It must not set terms requiring the purchase of other products or services as a condition of access. Penalties reach up to A$10 million for certain contraventions. Now the distinction that matters. The scheme regulates manufacturer-to-repairer service and repair information. It says nothing about a DMS vendor's charges for third-party access to a dealer's own operational data: your customer records, your stock, your invoices, your service bookings. Those are different data, different parties and a different relationship. State that reading as analysis rather than settled law. This research found no source confirming or disputing that the scheme excludes DMS vendors, and the mapping is our own reading of the scheme's definitions. The practical position is unchanged either way: if your DMS charges for API access or declines it, you have no obvious regulatory lever in Australia, and your only remedies are contractual and commercial.

When a DMS offers no API, five other channels exist and they are not equivalent. The differences that matter are reliability and whether the method is sanctioned by your DMS agreement. Reliability and risk assessments below are our engineering judgement applied to how each channel behaves in practice. | Method | How it works | Reliability | Terms of service risk | |---|---|---|---| | Vendor-certified API | Join the partner or certified vendor programme, receive credentials, call the documented endpoints | Highest. Bi-directional and real-time where supported | Lowest, but gated and often priced. Approval can be slow and can be withdrawn | | Scheduled CSV export to SFTP | You are set up as a vendor with DMS support, which then exports agreed columns on an agreed schedule to SFTP credentials. Described as a standard approach in Dealer Spike's DMS integration documentation | Good for anything tolerant of latency. Fragile to silent column changes and missed drops, so you need schema checks and drop detection | Low. It is a sanctioned channel | | Emailed scheduled reports | The DMS emails a report on a schedule and you parse the attachment | Workable. The mail path is the weak link, and format drift is common | Low, but operational data now sits in a mailbox, which is a privacy consideration | | Direct database access | A read replica or direct SQL against the DMS database, usually only possible on on-premise legacy installs | Very high fidelity, very high coupling. Upgrades change the schema and break you | Usually contractually prohibited. Needs written vendor sign-off before anyone connects | | Third-party middleware | A specialist extracts from the DMS and re-serves the data. Named examples include Amplify Analytics DMS Integrate and, in Australia, MyIntegrator | Shifts maintenance off your team. Adds a dependency and a per-dealer cost | Depends entirely on how the middleware gets its access. Credential-based access is the model the American litigation was about | | Screen scraping or reverse-engineered browser flows | Drive the DMS web interface, or replay its internal network calls, to synthesise an API layer | Lowest. Breaks on any interface change, with no support path when it does | Highest. Almost certainly breaches the DMS terms of service, and often depends on sharing a dealer's own credentials with a third party | Our position on the last row is firm. Screen scraping is not a durable architecture to recommend to a dealership, because the contractual and privacy exposure sits with the dealer and the failure mode is silent.

The reliability ceiling of any integration is set by the sanctioned channel the DMS offers, not by how good your build is. This is the single most useful test to apply to a proposal. Find out what channel the vendor formally supports, then check whether the promise being made to you is achievable through it. If the only sanctioned channel is a nightly CSV drop, a real-time integration promise is either a scrape or a fiction. There is no third option. Nobody can build sub-minute synchronisation on top of a file that arrives once a day, so either the build is quietly going around the vendor, or the word real-time is doing work the architecture cannot support. The right response is not to abandon the project. Design to the nightly CSV and be upfront about the latency. A stock feed that is accurate as at 2am, clearly labelled as such on the website and in internal reports, is a genuinely useful system. A stock feed that claims to be live and is actually twelve hours stale creates exactly the customer conversations you were trying to avoid. This also gives you a clean way to read a quote. Ask which channel the build uses. If the answer is vague, or if it describes real-time behaviour without naming a real-time channel, the latency question has not been answered and the reliability of the whole thing is unknown. A build honest about its refresh cadence is easier to operate than one that is optimistic about it.

Blackpurl has the most concretely documented Shopify integration in the powersports category, and the reason to trust it is that it quotes a cadence rather than a claim. Blackpurl's own documentation states the integration syncs both systems every 10 minutes, with online orders landing in the DMS within 15 minutes. It syncs stock availability, part record information and customer orders in both directions, and Blackpurl publishes support articles for setup and for processing a Shopify-originated sale. Note the commercial gating. The Shopify integration requires Blackpurl's Professional or Professional Plus package and carries an additional cost, with pricing available only through an account manager. That is the access-model pattern again, appearing even where the integration itself is well documented. The specificity is worth praising, because it is rare. A vendor that publishes a 10-minute polling cycle and a 15-minute order landing window has told you what to expect and what to design around. A vendor that says real-time sync has told you nothing you can plan against, and has left itself room to be right about a very different number. For Neto and Maropost merchants the finding is blunt. No DMS in this research names Neto or Maropost as an integration. That is verified by absence across two vendors' own published integration lists: Blackpurl's catalogue includes Shopify and does not include Neto or Maropost, and Titan's roughly 80-partner list does not include them either. Titan instead ships its own Parts eCommerce module, which names no third-party platform at all and reads as a first-party storefront rather than a connector. The realistic path for a Neto store is third-party middleware, not a native connector, and it should be scoped and priced as a build.

Before you plan any integration around a DMS, get written answers to six questions. Written matters. Verbal assurances about API access do not survive a change of account manager, and in a category where nothing is published, the email thread is your only documentation. One. Is there an API, and is it available on our contract and plan? Two. What does it cover, endpoint by endpoint, for the objects we actually need: customers, stock, service bookings, parts, invoices. Three. What does access cost, as a setup fee and as an ongoing fee, and is it charged per location. Four. What is the approval process, who assesses it, and how long does it take from application to credentials. Five. If there is no API, what is the sanctioned channel, at what frequency, and in what format. Six. Can we have all of that in writing. Question five is the one people skip and the one that determines your architecture. The answer sets your latency floor and therefore what you can honestly promise customers and staff. Question four sets your timeline, and in this category the approval wait is frequently longer than the build. If a vendor will not answer these in writing, that is itself an answer, and it belongs in your risk assessment before you commit a budget. It is also a reasonable thing to raise at renewal, when you have more bargaining power than at any other point in the contract.

Does my Australian DMS have an API? Probably, but you may not be able to find out by reading the vendor's website. Titan DMS advertises over 150 API endpoints and Keyloop publishes more than 30 API products with open documentation. Pentana describes tailored interfaces without publishing an API. Revolution DMS mentions no API on its motorcycle page, and Blackpurl still describes its API as upcoming. Ask in writing. What does DMS API access cost in Australia? No Australian DMS vendor publishes integration pricing. The only concrete figures found anywhere in this research were American, in US dollars, and posted to a dealer forum in 2017, where one dealer reported a per-location setup fee plus a per-location monthly maintenance fee for API access. They are not a guide to Australian pricing. Get a written quote from your own vendor. Can I connect a Neto or Maropost store to my DMS? Not through a native connector, based on what the vendors publish. No DMS in this research names Neto or Maropost as an integration, and their absence is confirmed by checking both Blackpurl's and Titan's own published integration lists. The realistic route is third-party middleware sitting between the two systems, scoped and costed as a build rather than switched on. Is screen scraping my DMS a reasonable option? No, not as a durable architecture. It almost certainly breaches the DMS terms of service, it usually depends on sharing a dealer's own login credentials with a third party, and it breaks whenever the vendor changes the interface, with no support path when it does. The contractual and privacy exposure lands on the dealership, not on the developer. Does Australia have a right-to-repair law that forces DMS vendors to share data? No. The Motor Vehicle Service and Repair Information Sharing Scheme, mandatory from 1 July 2022, requires vehicle manufacturers to supply service and repair information to all Australian repairers at no more than fair market value, with penalties up to A$10 million. It regulates manufacturer-to-repairer information, not a DMS vendor's charges for third-party access to your own operational data. Which DMS do most Australian motorcycle dealerships use? Nobody publishes the answer. GoAutoNews Premium reported in March 2024 that Pentana leads the broader Australian DMS market, with Auto-IT second and Titan third, but no market share percentages exist and no source breaks the motorcycle segment out. Titan names Motorcycle as a served industry, Blackpurl is powersports-first and Revolution DMS claims the motorcycle standard position.