Traverse Standard v11.0

Shopping Cart Integration Services

Traverse can integrate with e-commerce platform BigCommerce. This third-party Shopping Cart application give users a complete online shopping experience that ties directly to the Traverse backoffice. BigCommerce can handle coupons and discounts, as well as send emails with tracking information to end-customers to notify them of the shipment.

Using a standard Traverse synchronization process, this application will allow for automation of the ordering and payment process from the web store through the Traverse backoffice, and communicate the shipment process from the backoffice to the web store. For more information, see the Advanced Shopping Cart Integration Services topic.

The basic workflow includes two-way synchronization for customers and orders. Item synchronization is one direction: Traverse to BigCommerce. You have the option to disable each of these individually through the Process Shopping Cart function on the SO Transactions menu.

You have a choice of workflow scenarios when using BigCommerce:

You can enter all data in BigCommerce. In this case, BigCommerce would handle the item listing, pricing, customer list, etc. Orders flow to Traverse for processing and shipping status updates.
You can manage all data in Traverse. Items, pricing, and customers are maintained in Traverse; only orders would be processed through the shopping cart. Traverse would upload items, customers, and pricing details to BigCommerce.
NOTE: Lotted and serialized items will not be sent to BigCommerce if the Order Management setting is 'BigCommerce' (online), as BigCommerce has no way to handle lot or serial numbers. Any orders for lotted or serialized items will need to be handled solely in Traverse, or customized to handle them the way the customer specifies.

You have the option to manage data in either Traverse or BigCommerce. The organization decides which system is the primary system for maintaining data, while allowing exceptions to the rule when an order or product needs to be entered through the secondary system to complete the process. Regardless of the system chosen to manage data, orders should be entered in BigCommerce. For more information, see the Advanced Shopping Cart Integration Services topic.

In the System Manager Business Rules, in the SM Defaults – Services section, set the Default Shopping Cart Service to 'BigCommerce'.

NOTE: If you don’t see the Shopping Cart Integration Services menu in the System Manager Setup and Maintenance menu, unhide the menu through the SM Setup and Maintenance-->Application Menus function by clearing the Hide check box for Shopping Cart Integration Services. Enter 2 into the Parameters field to activate the BigCommerce selection. To add permissions to the function, use the SM Administration Groups function.

In the System Manager Setup and Maintenance menu, open the Shopping Cart Integration Services screen. Select 'BigCommerce' from the Name drop-down list. Once you select 'BigCommerce', the screen will display a number of data entry fields required for the integration to function properly. You must have a BigCommerce account created to obtain the credentials required for Traverse.

The values displayed are for OSAS testing purposes. You must obtain each value from BigCommerce via your account. You must have a BigCommerce account to obtain the credentials required for Traverse.

Enter the associated API credential provided by BigCommerce in the Consumer Secret Key field.
Enter the associated API credential provided by BigCommerce in the Store Host URL field.
Enter the associated API credential provided by BigCommerce in the Store Secret Token field.
Mark the New Customers check box to allow new customers to be created during the customer synchronization process.
Mark the Updated Customers check box to allow updates to existing customers during the customer synchronization process.
Enter a Customer ID Prefix if you would like to indicate customers created via your BigCommerce site/store. This number is appended to the beginning of the customer ID from BigCommerce when the customer is created in Traverse during synchronization, and allows you to see at a glance which customers were entered through BigCommerce.
Enter an AR Customer Template ID to use when synchronizing a customer you create via your BigCommerce site/store. Because Traverse has different requirements than BigCommerce when creating customer records, the template contains default values that fill in the required fields in Traverse, including Term Code, Group Code, Currency ID, Tax Group ID, etc. Note: Create a generic customer template for best results.
Enter an AR Guest Customer ID to use when synchronizing an order placed as a guest login via your BigCommerce site/store. This Traverse guest customer will include default customer information.
Be cautious about using a guest customer. If you have many customers placing orders using the guest customer, your open invoices and history for this guest customer can grow large very quickly and be difficult to manage and evaluate.
Note: Create a generic customer template for best results.
Mark the Push New Inventory Items check box to allow new inventory items to be created as products in BigCommerce during the Item synchronization process.
Mark the Push Updated Inventory Items check box to allow existing inventory items to be updated in BigCommerce during the Item synchronization process.
The Template Inventory Item ID field is not applicable at this time. Note: Create a generic inventory item template for best results.
Mark the Push Updated Orders check box to allow existing sales orders in BigCommerce to be updated during the order synchronization process. For more information, see the Advanced Shopping Cart Integration Services topic.
Enter a default inventory Location ID for quantity tracking, pricing, and creating sales orders. Items in this location will be available to be pushed into BigCommerce during the item synchronization process. This will be the only inventory location used for these items in BigCommerce.
Enter a default inventory Sales Category to use when creating a BigCommerce product by synchronizing a Traverse item that does not have a sales category. The sales category is not required in Traverse Inventory Item setup; however, it is required in the BigCommerce products.
Enter a default SO Transaction Batch Code. The batch code will be used by orders created by the synchronization process.
Enter a default SO Cash Receipt Batch Code. The batch code will be used by the payment record created by the synchronization process.
Enter your AR Store Credit Payment Method. This is the Traverse payment method recorded when a customer who orders through BigCommerce pays with store credit.
Enter your AR Gift Certificate Payment Method. This is the Traverse payment method recorded when a customer who orders through BigCommerce pays with a gift certificate.
Enter your AR Coupon Payment Method. This is the Traverse payment method recorded when a customer who orders through BigCommerce pays with a coupon.

NOTE: The previous payment methods must be set up in the Accounts Receivable Payment Methods function, using the 'Other' Payment Type with a GL Account that is for the appropriate type of payment (Not your cash account).

Enter your AR Other Payment Method. This is the Traverse payment method recorded when a customer who orders through BigCommerce pays with other payment methods.

NOTE: BigCommerce handles the credit card payments. Traverse will capture this as Cash.

Enter your Tax Class Mapping (Value array; i.e. {0,0;1,3;}). This maps the Traverse Tax Class (first number) to the BigCommerce Tax Class (second number).
Select the destination for your customers and customer updates when synchronizing from the Customer Synch Direction drop-down list. See the Manage Customers section in the Advanced Shopping Cart Integration Service topic for more information.
Select where you want to maintain your orders and updates to those orders from the Order Management drop-down list. See the Manage Orders section in the Advanced Shopping Cart Integration Service topic for more information.