QUESTION

=========

Because of our very peculiar and awful POS system, we only have the ability to send the data of customer's purchases in an ASCII text file. Is there a way to input those transactions?

SOLUTION

=========

[2009.03 - Update: The ability to upload our own data is now available in the application: Click on the "Manage Customer Records" on the control panel (the first page once you login) and then select either "Import Customers" or "Import Customer Transactions".  Instructions are on those pages.]

Yes, we do provide a way to enter a large amount of transactions at once, however it is not publicly available. The data file can needs to be formated in a variety of formats, and there is a charge for StickyStreet to process that file based on the amount of work that needs to be done to prep the file, if any is needed.  Because of the complexity of this topic, the best way to move forward is to talk to our support dept., which you can find on our contact page:

http://www.stickystreet.com/contact-us

Basically, you'll need the following files:

- The first one records the information about (new or updated) customers (name, email, phone, addt'l info, etc.)

- The second one is the transaction details for existing customers

The Transactions file needs to have each customer identified by a unique ID previously manually entered or provided as part of the Customer Information file to be batch-uploaded.  Both will need to be in Excel, CSV, or tab or pipe ( | ) separated.

The Customer Profiles file will need the following fields:

- The customer's account number or unique identifier (optional if you do not plan to send transactions batch files, or have your customers be able to lookup their account balances on your website.)

- Their First name (optional)

- Their Last name (optional)

- Their email address (optional)

- Their phone number (optional)

- Text with additional information  (optional)

The transaction details file requires the following fields:

- The customer's account number or unique identifier (required)

- The transaction amount (required)

- The campaign name the transaction belongs to (or say which campaign in the email to which this file is attached.)

- The date of the transaction (required)

- Whether it is an "add" event or a "redeem" event. (required)

- Optionally, a transaction description text.