How do you know whether a dealership integration is live?

Use a real record, not a test account

Vendor test environments are configured to work. Ask to see a record from your store, or a reference store on your DMS, move through the connection.

Check both directions separately

Reading and writing are different permissions and often different scopes. Confirm each direction independently, and confirm what happens on update and delete, not only on create.

Ask how failure surfaces

Establish what happens when the connection breaks: is anyone alerted, does the record queue or drop, and how would the store notice. Silent failure is the common case and the expensive one.

Get it in writing from both sides

The scope statement should come from both providers and should match. Where they disagree, that disagreement is the finding.

A short live-check routine

Choose a record type, make a small change in the source system, note the time and watch for the change in the destination. Record the delay, the fields that changed and any that did not.

Repeat with an update and a deletion. Save screenshots with timestamps.

A routine of ten minutes per integration gives evidence that a partner page cannot.

Monitoring after go-live

Ask how the store will know when a connection fails: alerts, a dashboard, a daily report. Assign a person to check it weekly.

Compare record counts across systems monthly. Ask the vendors to notify you before releasing changes that affect the integration and to provide release notes.

Monitoring turns a one-time verification into a continuing assurance.

Common mistakes in integration checks

Checking only when the connection is first installed, using a demonstration environment, testing one direction only and assuming silence means success are frequent. Another is failing to record who is responsible when it breaks. Put the check into your renewal and release calendar so that each change prompts a new test.

Who should perform the check

Choose someone who uses the data daily and understands what the result should look like, not only an administrator. Pair them with the person who can see logs in the system. Two people together can confirm both what arrives and what was sent, which quickly locates any problem.

Documenting for later

Save the test record identifiers, screenshots, timings and any error messages in the integration record. Note the version of each product tested.

When either vendor releases an update, repeat the test and compare with the saved results. Documented checks save time and give leverage when a vendor claims nothing changed.