RepSparks Guide to 811, “Call before you DIG”.

What is RepSpark’s 811 document?

This guide outlines the critical steps and responsibilities for any client, partner, or internal team member planning to make changes to their RepSpark configuration, integrations, or underlying data structure.

Why "Call Before You DIG" (Contact RepSpark First)?

The phrase "Call before you DIG" is a metaphor for engaging with the RepSpark team before initiating a change that could impact the stability, performance, or integrity of your RepSpark system.

Key Benefits of Contacting RepSpark First

Prevent System Downtime and Data Loss

Many changes (e.g., updating data mapping fields, altering custom fields, changing data structure) have unforeseen dependencies. Uncoordinated changes can instantly break integrations, halt order processing, and lead to end-user frustration.

Ensure Compatibility and Best Practices

RepSpark's architecture is complex and highly customized to meet your needs. Our team can advise on the proper methods for implementing changes, ensuring they align with current platform best practices and future upgrade paths.
We can confirm that your intended modification will work seamlessly with the existing integration or identify where RepSpark may need to adjust the integration to accommodate your changes.

When to Engage RepSpark

The following examples represent changes that frequently impact system stability or break integrations. This list provides helpful guidance on when to engage RepSpark to ensure stability and avoid disruptions.

Critical Data and System Changes

Category	Examples of Changes Requiring RepSpark Contact
ERP/Integration Structure	Changing field/table names in the ERP.
	API subscription key updates.
	Conducting a Sandbox Refresh (Applicable to NetSuite integrations).
Product & Inventory Data	Changing/adding/updating Item, Color, Gender, Warehouse, Customer, Store codes, etc.
	Updating inventory saved searches (Applicable to NetSuite integrations).
	Updating any Options Keycodes (e.g., color abbreviations, size codes).
	Deletion of records (Item, Color, Gender, Size, Warehouse, etc.).
Pricing	Making mass pricing updates.
Configuration	Changing the timing of data or image asset posts to FTP.
	Changing field formats (e.g., boolean to text/string).
	Changing query language associated with data exports to RepSpark (e.g., inserting new logic).

Business and Expansion Changes

Category	Examples of Changes Requiring RepSpark Contact
Expansion/Divisions	Adding a new region or division to your business.
	Implementing Insignias for a new brand or division.
	Onboarding a 3rd party decorator (e.g., Epic Stitch).
	Adding more users or microsites (contact your account manager).
System Upgrade	Upgrading to a new ERP.
Sales & Customer Management	Changing sales reps in an existing territory.
	Adding new values to existing logical fields (e.g., adding new customer types or segmentation channels, which may drive access to order types, pricing, or products).
Pricing Structure	Adding new pricing tiers or pricing plans.
	Reconfiguring existing size ranges in your ERP.

Example Scenarios and Recommended Action

Scenario	Recommended Action (Call RepSpark)	Rationale
Product, Color, or Size is no longer offered and shouldn't be available to order.	Contact RepSpark to coordinate the disabling of the record.	Disabling the record ensures it no longer appears for new orders but preserves necessary historical data for orders, order history, and reporting. RepSpark strongly recommends disabling over deletion.
Customer or Sales Rep is no longer with the company and should not appear in searches.	Contact RepSpark to coordinate the disabling of the user/record.	Disabling ensures visibility in other areas of the site (Orders, Order History, Customer records, etc.) while preventing new transactions.
User deletion vs. archiving/disabling.	Always consult RepSpark regarding the proper method for user management.	RepSpark recommends disabling/archiving records to maintain data integrity and visibility for historical purposes.