ScanSource Integration: Prerequisites

Before configuring the ScanSource integration, ensure the following prerequisites are in place.

ScanSource API Credentials

API access must be enabled on your ScanSource account before the integration can connect. Contact your ScanSource representative to request access to the Product API if you do not already have it. The integration requires the following credentials.

• Scopes - the Product API application ID with the /.default suffix, used for the client credentials grant.
• Client ID - the OAuth2 Client ID from your ScanSource Bullfrog application registration. This is distinct from the subscription key.
• Client Secret - the OAuth2 Client Secret paired with your Client ID. Store this securely and rotate it per your partner policy.
• Subscription Key - your ScanSource Azure APIM subscription key, issued through the ScanSource Partner Portal. The primary key is recommended, though the primary and secondary keys are interchangeable.
• Customer Number - your ScanSource partner/reseller account number, also referred to as your Organization Identification in the Partner Portal. Maximum 10 characters.

Keep these credentials available during configuration.

Product Catalog Preparation

For the integration to recognize and update your ScanSource products, your product catalog must be prepared as follows.

• Products already linked to ScanSource must have the ScanSource item number in the SKU/USOC field on the ScanSource vendor line.
• Products not yet linked to ScanSource must have an accurate Manufacturer Part # on the product record. The integration uses this value to find the matching ScanSource item and link it automatically.

Manufacturer part number matching is not case-sensitive and ignores extra spaces, but the full part number must match exactly. Products without a matching manufacturer part number will not be linked.

Once your ScanSource credentials and product catalog are ready, see the ScanSource Integration: Configuration article to complete setup.