SASA SHOP OS · INTEGRATIONS

Start with what
needs to connect.

Connect the tools and records your workshop relies on. Bring parts, accounting and customer communication into a coordinated workflow.

Workshop manager and parts coordinator reviewing their systems at a service desk

Verify the connection, not just the name.

SaSa Shop OS supports integration workflows for shop records and connected services. Review your providers, required operations and account editions with the team to confirm the right configuration.

Ask the SaSa team to confirm current availability, supported operations and any account or commercial requirements for each connection your shop needs.

Put each requirement in context.

Parts & technical information

Name your supplier or information source. Distinguish searching a catalog from ordering, receiving stock or accessing licensed repair information.

Supplier requirements

Records & accounting

Identify which customer, vehicle, stock or invoice records need to move, in which direction, and how corrections should be reconciled.

Data and agreement questions

Customer communication

Separate stored conversation notes from sending messages. Define recipients, consent, channels and how delivery failures should be handled.

Communication requirements

Bring a connection brief to the conversation.

  • System and version. Name the product you use and the account owner who can confirm access.
  • The actual task. Specify the records or events involved, who starts the action and the expected result.
  • Direction and timing. Explain whether information must move one way or both ways, and how current it needs to be.
  • Exceptions. Include duplicates, changed records, rejected requests and what should happen when a service is unavailable.
  • Access and responsibility. Identify who may view, change or export the information. Do not send access tokens or customer data.
  • Commercial scope. Confirm supported plans, provider subscriptions, additional charges and who maintains the connection.

Request a demonstration of the agreed scenario in the actual application before making it part of your operational plan. Confirm provider editions, API access and any separate subscription requirements for your configuration.

Bring your systems. And your questions.

Use an anonymized workflow to explain the outcome you need. The team can then discuss what is currently supported and what needs further review.