Summary

Creating a New CCC Account

Settings

General Settings

• Supplier ID (Assigned to Us): This is the ID that CCC has assigned to you.  This is crucial for the integration to work.
• Address and Contact Info Fields...
• Email Notification:
• Fall Back Customer:  If an Order is sent to X customer, which does NOT exist in 1place, you can create a 'Fall Back' (default) customer, such as New CCC Order, and select that customer for this field.  This will allow you to not LOSE the Order and also know when a new Customer needs to be added to 1place that matches their Repair Facility ID (RFID). 
• Sales Person:
• Part Type Override:  
• Default Quality Indicator:
• Delivery Cuttoff Time:  This is the time of day that differentiates if the item will be delivered the same day, or without adding another day.  Here are some scenarios to make it more clear: 
• Scenario 1: Suppose you set 12:00pm as the cutoff time, and a new Sales Order comes in at 11am.  The Estimated Delivery Date will be Today.  Next it looks for a ZIP Code in the Delivery Area Zip Codes and checks the # Days to Add.  If that value is 1, then the Estimated Delivery Date (shown in CCC) will be Tomorrow.
• Scenario 2: Suppose you set 12:1am as the cutoff time, and a new Sales Order comes in at 11am.  The Estimated Delivery Date will be Tomorrow.  Next it looks for a ZIP Code in the Delivery Area Zip Codes and checks the # Days to Add.  If that value is 1, then the Estimated Delivery Date (shown in CCC) will be 2 days from now.   
• Scenario 3: Suppose you set 12:1am as the cutoff time, and a new Sales Order comes in at 11am.  The Estimated Delivery Date will be Tomorrow.  Next it looks for a ZIP Code in the Delivery Area Zip Codes and checks the # Days to Add.  If that value is 1, then the Estimated Delivery Date will be 2 days from now. But if the item needs to be transferred from another warehouse (in your Region) and the # Days to Add for Stock Transfer value = 1, then the Estimated Delivery Date (shown in CCC) will be 3 days from now.   
• # Days to Add for Stock Transfer: This is the # of days to ADD to the Estimated delivery date if the item needs to be transferred from another warehouse to the warehouse that will be delivering the Order.
• Default Lead Time if Out of Stock (Number of Days): (This is not in use at this time). 
• Preparation Lead Time: (This is not in use at this time).
• Show Out of Stock Items:   (This is not in use at this time).
• Use Supplier Qty:  
• Auto Ship New Orders:
• Warranty Type:  This might have a value such as: Limited. 
• Warranty Length:  This might have a value such as 90 Days, or 1 year, etc
• Warranty Info: This can give the customer more details or a message such as:  Please call for more details.

Part Type / Code Mapping

• There is a 'Quality Indicator' field on the Item Detail record (for each unique item).  
• If the item is Aftermarket you might enter an A in the Quality Indicator field.
• If the item is CAPA Certified you might enter a C in the Quality Indicator field
• If the item is Reconditioned you might enter an R in the Quality Indicator field
• If the item is OEM you might enter a OE or OEM in the Quality Indicator field
• If the item is an Optional OEM part you might enter OptOE in the Quality Indicator field
• Etc.
• If CCC Requires a CAPA part to be listed as CAPA (on their side) and PartsTrader Requires a CAPA part to be list as C (on their side), you cannot have 'both' values.  This table allows you to have your own 'Quality Indicator' and then 'translate the Quality Indicator to whatever value CCC or another other integration partner requires on their side. 

Delivery Area Zip Codes

• This table helps the API determine the (1) Which zip codes do you sell/delivery to?, and (2) How many extra days need to be added to the Estimated Delivery Date, based on each unique Zip Code.
• This table has these columns:
• Zip Code: Enter ALL zip codes that you service
• Warehouse: This is just for reference.  This value is not used in the calculation.
• # of Day to Deliver: This # tells the integration code how many 'extra' days to add to the Estimated Delivery Date, if the Customer resides in that Zip Code. See the notes about the 'Cuttoff Time' field in the General Settings above to get more clarity.    
• X: Click the X icon to delete the row.

Warehouses

• Enter your Warehouses in this table.

File Transfer

• This is used to create a set of data about your company, your warehouses, your items, your zip codes, etc.
• It also contains various options of how to deliver the files to the integration partner.

Testing

GoLive

CCC True - Shop Registration

Overview

The CCC Shop Registration feature allows 1place to register a customer with the CCC True integration service. Once registered, the customer is authenticated with CCC, enabling integration features that require shop registration.

The integration supports two deployment models:

• Standard (Non-KSI) Customers – Uses the shared 1place integration server and credentials.
• Dedicated Integration Customers (such as KSI) – Uses the customer's own integration server and authentication credentials.

Based on the configuration, 1place automatically determines which authentication method to use.

Accessing API Integration Details

Navigate to:

Sales → Integration → CCC True → API Integration Details

This screen is used to configure the Shop Registration feature.

API Integration Settings

The API Integration Details screen contains the following settings.

Enable Shop Registration

Enables or disables automatic CCC Shop Registration.

When enabled, 1place automatically attempts to register customers configured for the CCC True integration.

If disabled, customer API information is saved, but no registration request is sent.

Integration Server Details

These fields are intended only for customers using their own dedicated integration environment.

Standard customers should leave these fields blank.

Integration Credentials

Enter the authentication credentials for the dedicated integration server.

Standard customers should leave these fields blank.

Configuration Scenarios

Scenario 1 – Standard (Non-KSI) Customer

Customers using the shared 1place integration service should:

1. Enable Shop Registration.
2. Leave the Integration Server and Credential fields blank.
3. Save the configuration.

When the server and credential fields are blank, 1place automatically uses the shared OneSource integration credentials.

No additional configuration is required.

Scenario 2 – Dedicated Integration Customer (KSI)

Customers with their own integration environment should:

1. Enable Shop Registration.
2. Enter the Integration Server information.
3. Enter the authentication credentials.
4. Save the configuration.

The system will authenticate using the customer's dedicated integration environment.

Shop Registration Workflow

Shop Registration begins whenever:

• A customer's API Type is configured as CCC True.
• Enable Shop Registration is enabled.

Standard (Non-KSI) Customer Workflow

When Integration Server fields are blank, the system:

1. Verifies that Shop Registration is enabled.
2. Uses the shared OneSource integration credentials.
3. Validates the authentication token.
4. Registers the customer with CCC.

Once registration is successful:

• The customer is marked as registered.
• Future manual registrations and scheduled registration jobs will skip the customer unless they are unregistered.

Dedicated Integration Customer Workflow

When Integration Server information has been provided, the system:

1. Verifies that Shop Registration is enabled.
2. Uses the configured Integration Server and credentials.
3. Validates or generates an authentication token.
4. Registers the customer with CCC.

Once registration is successful:

• The customer is marked as registered.
• Future registration attempts are skipped unless the customer is unregistered.

Shop Unregistration

Removing the CCC True API configuration from the customer's API settings automatically initiates the Shop Unregistration process.

The system uses the same authentication method that was used during registration.

• Standard customers use the shared OneSource integration credentials.
• Dedicated customers use their configured Integration Server and credentials.

Important Notes

• Shop Registration must be enabled before registration can occur.
• Standard customers should leave the Integration Server and Credential fields blank.
• Dedicated Integration customers must provide their own server information and credentials.
• A successfully registered customer will not be registered again unless they are first unregistered.