Skip to content
English
  • There are no suggestions because the search field is empty.

Setting up customers

This guide walks you through setting up customer data in RepSpark, covering the specific data fields required from your ERP system. The setup process varies by integration type: Shopify tags for Accelerate integrations and comprehensive data mapping for API/Flat-File integrations. RepSpark developers typically build the integration to map your ERP data, though some brands prefer to build their own API integration.

Overview

Customer setup in RepSpark involves mapping your existing customer data from your ERP system into RepSpark's customer structure. This ensures your B2B customers can access the platform with proper pricing, sales rep assignments, shipping methods, and payment terms. The data requirements and setup process depend on your integration type.

How it works

RepSpark creates customer records that include both billing and shipping addresses, sales rep assignments, pricing tiers, and access permissions. For Shopify integrations, this data flows through specific tags. For API and flat-file integrations, comprehensive customer records are created with detailed field mapping from your ERP system.

Before you start

Make sure you have the following:

  • Access to your ERP system's customer data
  • List of active customers who need RepSpark access
  • Sales representative assignments and codes
  • Customer pricing tiers and discount structures
  • Shipping method preferences per customer
  • Payment terms for each customer account
  • For Shopify integrations: Admin access to add customer tags
  • For API integrations: Development resources or RepSpark developer support

Steps

For Accelerate (Shopify) Integrations

Customer data for Shopify integrations uses specific tags applied to customer records in your Shopify admin.

Tag name Required Format Example Usage
Wholesale Required Input Wholesale This tag lets RepSpark know that this is a Wholesale Customer and will be synced over to your Site.
SalesRep Required Input:Value:Label SalesRep:222:Bob Jones This tag will allow you to set up your different sales reps and associate them to your different customers. B2B users will need to have a Salesperson Code and their Customer Code to have access to RepSpark.
Terms Required Input:Value:Label Terms:Net30:Net 30 This tag shows you in RepSpark what payment terms this Customer has set up in Shopify
Shipping Required Input:Value:Label Shipping:UPSG:UPS Ground This tag shows you in RepSpark what Shipping Terms this Customer has set up in Shopify
Discount Optional Input:Value Discount:20 This tag is optional. This allows a specific Customer to have a Discount price on top of the Wholesale price. 
CustomerCode Optional Input:Value,
Input:Value:Value
CustomerCode:JT123,
CustomerCode:JT123:001

This tag will be helpful to invite your buyers.

By creating a Customer Code and sharing with your users, they will be able to sign up easier, and will be easier for you to search for them compared to typing out their entire name.

NOTE: The store# is not necessary, but helpful if the Customer has multiple locations/stores with different addresses.

 


For API & Flat-File Integrations

API and flat-file integrations require comprehensive customer data mapping from your ERP system. RepSpark developers typically handle this integration, though some brands build their own API connections.

Field Required Usage Notes
DivisionCode Optional DivisionCode allows you to arbitrarily segment data for security and visibility purposes. Divisions are versatile and can be applied to distinguish various elements such as geographical regions (e.g., North America vs. Europe), business verticals (e.g., wholesale vs. ecommerce), or even brands. Requires associated Option resource with an ElementType of DIVISION.
CustomerCode Required

A unique identifier that represents a group of Customer records.

CustomerCode maps to a higher level concept of a customer with a billing address and one or more shipping addresses. This supports both department store chains with a single billing address and many shipping addresses, and also a standalone country club with different billing and shipping addresses. Each of these addresses map to a Customer record with the same CustomerCode value.

 
StoreCode Required Represents an individual retail location for the Customer, primarily used for the shipping address of an order.  
Name Required Customer/Bill-To Name  
DBA Optional Alternate name a customer is doing business as.  
Address1 Required Street address line 1  
Address2 Optional Street address line 2  
City Required City  
State Required State  
Zip Required Zip  
Country Required Country  
PhoneNumber Optional Phone  
FaxNumber Optional Fax  
SalesPersonCode Required

A label that maps the Customer to their associated sales representative.

Sales person names are defined as Option resources with an ElementType of SALESPERSON.
ShippingMethodCode Optional The default shipping method defined for the Customer. Shipping method names are defined as Option resources with an ElementType of SHIPPINGOPTION.
DiscountPercentage Optional

A percentage discount that applies to all orders placed by this Customer by default. This discount can be overridden by users with the correct permissions as well as custom logic implemented specifically for your brand.

Numbers greater than 1 are divided by 100. For example, a value of 40 is treated as 40% off, and a value of 0.4 is also treated as 40% off.

 
TermsCode Optional Payment Terms Terms names are defined as Option resources with an ElementType of TERMS.
TypeCode Optional A short label that arbitrarily groups Customers.  
Enabled Required

Customer is active true/false.

Visible in the UI when true, hidden when false.

Often used to hide billing Customers, those with IsBillTo set to true, from the UI. This allows sales representatives to only select from the shipping addresses, usually those with StoreCode populated, that they have access to.

 
IsBillTo Optional Marks a Customer as a billing address. When IsBillTo is true, Enabled is often set to false to hide the record.