Where Do The Customer Orders Come Out?

Orders can be viewed or printed from Database Records or cc: copies of e-mail. The SendSafe system can be setup to automatically perform B2B order fulfillment with any offsite fulfillment center you may use. SendSafe also offers fully integrated RMA product return systems.

Some e-stores of almost any sales volume level opt to use the optional integrated fulfillment system to manage the flow of orders to their business (even when they do not use outside fulfillment centers). This setup provides both web-based and email-based fufillment options. For web-based operations the system shows lists of orders to be fufilled and provides the tools to fufillment them. In email-based the system will e-mail the e-store or fulfillment center a consolidated list of all orders which need to be processed today. This e-mail list will include all information needed for fulfillment. The e-store or fulfillment center then sends back to SendSafe a list of tracking numbers and ship dates which have been assigned to each lineitem in the order. SendSafe will automatically import this list and update ship status.

SendSafe also includes integrated support for performing immediate fulfillment of orders of digital products. Music, software, images, and more can be immediately provided for download to a customer after their charge has been approved.

In addition to what is described below, the bidding admin page should be used for viewing and working with custom products which use FFPs to describe the lineitem or for jobs which you are bidding using the integrated bidding system. See also: Bidding System for additional information.

Regardless the process used for handling orders, it is always a good idea to retain a copy of all cc: emailed receipts as a backup record of every order.

Low Volume E-Stores
Some low volume e-stores chose to keep it simple and drive their order processing directly from the cc: copy of the e-receipt which they receive. This e-receipt is a complete copy of what the customer received and includes all product pick, billing, and shipping information that would be needed by accounting and warehouse personnel. A slightly more automated solution is to use SendSafe's Web-based Fulfillment system (some customization by CPrompt my be required).

Medium Volume E-Stores
Medium volume e-stores often use one of the following:

• Web-based Fulfillment
• Accounting report
• An automated DB export job which creates a spreadsheet of daily sales that can be downloaded
• A custom report create for them by CPrompt to list and process orders.

An alternative is the optional accounting report which allows you to create a report which list all orders which came in on a specific day or for a specific customer on a specific day. You can click on an order to get a printable copy which includes all billing, shipping, and product pick information that would be needed by accounting and warehouse personnel. This printed copy can be used as a product traveler. The report can be customized by CPrompt to print shipping labels, barcoded travelers, bills of lading, or even thank you letters.

This report can also be exported in a comma delimited format which can be imported by accounting programs, shipping programs, or other software like spreadsheets. The report flags all exported orders, so that you will not end up with duplicates.

The contents of the customer and sales reports are configurable (to some extent) in the information printed for each order or customer.

CPrompt can create for your business "simple to use" reports and data entry screens designed for warehouse employees. These reports and data entry screens can contain consolidated inventory pick lists, order assembly instructions, forms, etc. These screens can work with barcode scanners and can track which employee handled which order. There is no limit to what can be done with custom reports and data entry screens.

High Volume E-Stores
High volume e-stores often have their accounting, call-center, inventory, and shipping systems integrated directly with SendSafe⁽¹⁾.

All orders as they are receive by the e-commerce system will be automatically inserted into your existing accounting, call-center, inventory, and shipping control systems. You will not need to change a single internal business procedure while introducing e-commerce into your business.

SendSafe can also be customized to print inventory pick lists, barcoded travelers, or any other type of custom paperwork your business may need (which cannot be produced by your accounting or inventory control systems).

⁽¹⁾Customization of SendSafe by CPrompt is often required for full automated solutions; semi-automated solutions may not require customization when 3rd part import tools are used. VPN network connections are also sometimes required.

Automated Fulfillment Overview

This FulFillment functionality is an optional add-on to the basic SendSafe system and may require some customization. The system fufills order and tracks the delivery of the products via outside fulfilment centers or Web-based.

The Fulfillment subsystem can be used in two ways:

• Process orders through an outside fulfillment companies
• Process orders for Web-based fulfillment

There are four different fulfillment methods in SendSafe:

• Mode A: B2B EMail-Based Post Processing of shippable Product fulfillment where a physical product is shipped by the fulfillment house under instructions automatcially issued to them from the SendSafe system. Formats 1800 & 1900 are supported; custom format can be added by CPrompt (additional development cost would apply).

• Mode B: Web-based processing of shippable product fulfillment where a physical product is shipped by an in-house department or fulfillment center.

• Mode C: Onsite Integrated Digital Payload Fulfillment where the payload is a set of files assembed locally by the SendSafe system and delivered to the customer via download from the SendSafe system. For more information see digital payloads.

• Mode D: Offsite B2B Digital Payload Fulfillment where the payload is assembed offsite by a B2B fulfillment house and delivered to the customer by the fulfillment house.

Shippable Products
Setup For Fulfillment of Shippable Products

Here are the basic steps for Mode A:

1. Designate all products in the DB which will be fulfilled by SendSafe
2. Setup an E-Mail Account for use by the robot to receive response back from the fulfillment house.
3. Setup the Initiation Job for shippable products. This is the job which transmits fulfillment instructions.
4. Setup the Status Update Job. This is the job which receives fulfillment updates from the fulfillment center.
5. Configure the Robot to perform B2B Fulfillment.

Here are the basic steps for Mode B:

1. Designate all products in the DB which will be fulfilled by SendSafe
2. Setup the Initiation Job for shippable products. This is the job which completes fulfillment.
3. Configure the Robot to perform Web-based Fulfillment.

An SQL Script is included with SendSafe which can be used to setup the jobs used to run B2B E-Mail based or Web-based Fulfillment. The name of this script is: Add B2B Fulfillment jobs.sql and Add e-mail or Web-based Fulfillment jobs.sql

Incoming E-Mail Account
This account is used by the robot to receive e-mail from the Fullment house. This account must be reserved only for use by the robot.

Designating Items for fulfillment

Shippable Items in the database designated as "B2B fufilled" will be processed by the B2B fulfillment system. Items are designated B2B by prefacing the Payloadloc field with an '@' sign or a "#' sign. The value after the '@' or '#' sign can (optionally) be used to identify the item to the B2B fulfillment house. This value is typically the product SKU, but it can be any alphanumeric designation you need.

Mode A & B: Payloadloc fields prefaced with a '#' will be fulfilled using integrated B2B for shippable product fulfillment. Typically an entry will be #<Optional Code> where the optional code can be used to further identify ITEMS for Mode A or Mode B (this optional field is reported while ignored by SendSafe logic and can be any code you want). The typical value is product SKU. ExamplePayLoadLoc = #HSJ-123 or ExamplePayLoadLoc = #MODEA or ExamplePayLoadLoc = #ANYTHING

Mode C: Payloadloc fields prefaced with a '@' will be fulfilled using plugin B2B fulfillment for offsite digital product fulfillment.

Mode D: Payloadloc fields prefaced with NEITHER an '@'or '#' will be fulfilled immediately in a locally assembled digital payload.

VERY IMPORTANT: Do not put only the prefix code into the Payloadloc DB column. This will result in orders for the product going unprocessed. YOu must have both the prefix (# or @) + some text string following it.

See for details

• Fulfillement Request E-Mail
• Fulfillement Completed E-Mail

Order Cancellation

The system can cancel an order either via a customer command on the thankyou page or by voiding it on the order admin page.

The B2B cancellation request will only be sent to the fulfillment email addresses if a ship order has been transmitted.

Inventory on an items will only be decremented if a ship confirmation has not been received from fulfillment.

Setup:

• Application("EnabledOrderVoiding") = true
• Application("FulFillmentB2BEMailList") = "myname@company1.com;info@b2b.com"
  list of people who are emailed a cancel ship request.
• Application("FulFillmentB2BCancelOrderMsg") = "You are authorized to cancel this order."
  Message in the cancel ship request email.

Fulfillment DB Table - OrderPostProc Table

The OrderPostProc table contains information on state of fulfillment including B2B and Web-based. These are examples of what can be seen in this DB table AS orders move down the assembly line (a.k.a. as steps of fulfimment are completed).

Example of a non-fullment order:

transactionid	ProcessStep	AcklFulFillmentCompleted	PostProcStatus
28897	NULL	NULL	{COMPLETED};E-RECEIPT PROC:SENT

Example of an order ready for fullment transmission or Web-based:

transactionid	ProcessStep	AcklFulFillmentCompleted	PostProcStatus
28897	1	NULL	{COMPLETED};E-RECEIPT PROC:SENT

Example of an order which has been transmitted to the fulfillment center or Web-based charge capture is in progess:

transactionid	ProcessStep	AcklFulFillmentCompleted	PostProcStatus
28897	2	NULL	{COMPLETED};E-RECEIPT PROC:SENT

Example of an order which has recieved from the fulfillment house that the order has shipped or Web-based charge capture is complete (order is okay to ship):

transactionid	ProcessStep	AcklFulFillmentCompleted	PostProcStatus
28897	3	NULL	{COMPLETED};E-RECEIPT PROC:SENT

Example of ship Acknowledgement e-mail has been sent and order fulfillment is complete:

transactionid	ProcessStep	AcklFulFillmentCompleted	PostProcStatus
28897	4	Jul 13 2004 2:59PM	{COMPLETED};E-RECEIPT PROC:SENT;FULFILLED

Example of a fullment order which has encountered an error:

transactionid	ProcessStep	AcklFulFillmentCompleted	PostProcStatus
28897	0	NULL	{COMPLETED};E-RECEIPT PROC:SENT

Shippable Products
Configuration of Robot for Modes A & B

FILE = "..\SendSafe\<your store name>.store.config" Before modifying any configuration file always make a backup copy of the file. To find a specific storefronts configuration file: see Location of Configuration files
Keyword	Default value	Explanation
B2B INTEGRATED	YES	This keyword enabled and disables B2B and Web-based Fulfillment operations

These three entries all set to YES will result in a serializer being assigned to the order ONCE the charge has been approved.

SERIALIZER	YES	This keyword enabled and disables serializing orders.
ONLYSERIALIZE B2B	YES	This keyword controls whether only B2B and Web-based fulfilled order recieve a serializer.
B2B POSTPROC	YES	This keyword enabled and disables Built B2B post processing Fulfillment operations (for shipable products). Post processing involves assigning a serilizer to the order.
B2B MODULE LOC	<none>	Set to "<none>" will disable - This entry is used for a B2B digitial fulfillment plug in module.
B2B MODULE NAME	<none>	Set to "<none>" will disable - This entry is used for a B2B digitial fulfillment plug in module.

Web-based Fulfillment Mode-B

Web-based fulfillment is controlled by using the Fulfillment admin page (located in the orders dropdown). This system is for 100% In-House fulfillment of orders OR for fulfillment houses which prefer to use a web based interface instead of email base data exchange.

This fulfillment function is fully integrated with SendSafe and does not require a B2B plugin module.

Web-based fulfillment works on orders as a whole, though you can designate different tracking # for different line items. Unlike B2B fulfillment, Web-based fulfillment will sweep all lineitems through the fulfillment process as long as one item or more in an order is flagged with the "#" in Payloadloc DB column and the ProcessStep=2.

Web-based fulfillment partially supports split shipments, but does not check for allocation of items to tracking numbers as format1900 does.

Basic steps of Web-based fulfillment:

1. Order fulfillment admin page lists all orders which are pending fulfillment
2. Tracking numbers are assigned individually to lineitems or globally to all items in an order. If you do not have a tracking number then enter the name of the carried (i.e. USPS, UPS, FedEx, etc). Failure to do this will result in the order NOT showing as shipped on the order status web page.
3. Optionally the order can be modified using the order and lineitem admin pages.
4. The order [Settlement] button is pressed on the order admin page
5. If the order had "charge holds" i.e. "delayed capture" is needed, those holds are now automatically captured and then potentially settled through the payment gateway and the order is flagged orders.status = "{COMPLETED};{CAPTURED};..."
6. Your order has shipped email is sent out
7. Orders.ProcessStep is advanced to step 4 (complete)

Back-ordered items:
Any lineitem can be flagged as backordered. If an order contains backordered items and the settlement button is pressed then the credit card charge will be captured (if relavent), but no "Your order has been shipped" email will be sent to the customer.

An lineitem is set as backordered when when the orderlineitem.ShipMethod field has the string "(BACKORDERED)" in it.

An order is set as backordered when when the orders.status field has the string "BACKORDERED" in it.

The Admin sets the orderlineitem.ShipMethod "(BACKORDERED)" flag using the admin page. The Fulfillment Job (type 41) sets the orders.status field has to "BACKORDERED." This state change will not be made until the order has been released for processing and (optional capture) credit card processing has completed. So any order is not considered in backorder status until it had bee released.

General Notes:

• Only the ICZ Credit card processing subsystem will provide automated charge settlements.
• The SQL Selection logic includes orders.storefrontName; as a result, you will need one fulfillment job for each storefront. This provides added flexibility and in handling and format of email responses.
• For PayFlowPro gateway users using delayed capture, make sure that referenced transactions are enabled (otherwise errors will result such as error code: 177).
• You do not have to run the "Order FulFillent 41" job if all you want is entry of tracking numbers and/or order ship status.
• If a fatal processing error occurs, such as CAPTURE declined, the Orders.ProcessStep is set to zero.

This function is run by an Order FulFillent 41 job which looks like the example below:

FORMAT1800 Shippable Products Mode-A
Transmission of ship instructions

This B2B function is fully integrated with SendSafe and does not require a B2B plugin module. This system will send ASCII TEXT e-mail to the fulfillment house and process a return ASCII TEXT e-mail from the fulfillment house containing order shippment status. This function can also be used in-house as a means of initiating the warehouse stage of product handling.

At a preset time each, a consolidated list of items which were ordered that day and require fulfillment is automatically e-mailed to the fulfillment house.

Very important: You must limit the size of your SQL queries to 250 records (i.e. TOP 250). Unlimited queries can result in very large e-mails which may clog up some systems. The system will reject SQL which does not include a TOP 250 limit. If you have more than 250 records the system will automatically spawn new jobs to handle each 250 records chunk until all orders have been processed.

Very important: You must order your queries by order by orders.transactionid. Failure to order your queries by transactionid will result in missing or duplciate entries if you have more than 250 items returned by your query.

This function is run by a JobQueue job which looks like the example below:

Example of SQL which will generate a list of orders suitable for import into UPS Software:

select top 250 orders.transactionid, 
company, 
name, 
address, 
city, 
state, 
zip, 
country, 
phone, 
'Prepaid', 
'Package', 
shipmethod, 
STR( sum( ShipWt * quantity ),10,2), 
email, 
'Y', 
' ' 
From OrderLineItem, addresses, orders, Items, orderspostproc 
where OrderLineItem.ShiptoAddressID = addresses.addressCodeId AND 
OrderLineItem.transactionid = orders.transactionid AND 
OrderLineItem.transactionid = orderspostproc.transactionid AND 
OrderLineItem.ItemCodeId = Items.ItemCodeId AND 
Items.PayLoadloc like '#%' AND 
ProcessStep = 1 AND 

orders.date < CAST( CAST ( DATEPART(MONTH, getdate() ) AS char ) + '/' + 
CAST ( DATEPART(DAY, getdate() ) AS char ) + '/' +  
CAST ( DATEPART(YEAR, getdate() )  AS char ) + ' ' + ' 23:00' + ' ' AS datetime) 
group by orders.transactionid, 
company, 
name, 
address, 
city, 
state, 
zip, 
country, 
phone, 
shipmethod, 
email 
order by orders.transactionid

Example of SQL which will generate a list of order lineitems suitable for processing by a fulfillment center:

Select top 250 orders.transactionid, 
serializer, 
date, 
LineItemID, 
sku, 
fullname, 
itemparameter, 
quantity, 
STR( OrderLineItem.priceea, 10,2), 
shipmethod, 
STR( ShipWt * quantity, 10,2), 
requiredshipdate, 
name, 
company, 
address, 
city, 
state, 
zip, 
country, 
phone, 
email, 
fax, 
altphone, 
international, 
STR( subtotalitems, 10,2), 
STR( subtotalshipping, 10,2), 
STR( subtotalsalestax, 10,2), 
STR( totalamount, 10,2) 
From OrderLineItem, addresses, orders, Items, orderspostproc 
where OrderLineItem.ShiptoAddressID = addresses.addressCodeId AND 
OrderLineItem.transactionid = orders.transactionid AND 
OrderLineItem.transactionid = orderspostproc.transactionid AND 
OrderLineItem.ItemCodeId = Items.ItemCodeId AND 
Items.PayLoadloc like '#%' AND 
ProcessStep = 1 AND 

orders.date < CAST( CAST ( DATEPART(MONTH, getdate() ) AS char ) + '/' + 
CAST ( DATEPART(DAY, getdate() ) AS char ) + '/' +  
CAST ( DATEPART(YEAR, getdate() )  AS char ) + ' ' + ' 23:00' + ' ' AS datetime) 

order by orders.transactionid

Format of "Fulfillment Request" outgoing E-Mail

The e-mail which is sent to the fulfillment house is a comma delimited file containing all orders placed up to the cut off time each day. The specific fields and order of appearance is defined in param2 of the Job (see above). Any column from these tables can be included in the outgoring transmittal:

• OrderLineItem
• addresses
• orders
• Items
• orderspostproc

The example below contains the following fields in the specified order. Field selection and order is made by configuring the Post Processing Job.

orders.transactionid
serializer
date
LineItemID
sku
fullname
quantity
STR( OrderLineItem.priceea, 10,2)
shipmethod
name
company
address
city
state
zip
country
phone
email
altphone
STR( subtotalitems, 10,2)
STR( subtotalshipping, 10,2)
STR( subtotalsalestax, 10,2)
STR( totalamount, 10,2)

FORMAT1800 Shippable Products Mode-A
Ship instructions executed message

E-mail is sent from the fufillment house to the e-commerce system to update fulfillment status. This e-mail contains shipment tracking and other information which is automatically imported into the SendSafe database and presented to the customer on their order status pages. The receipt of this e-mail also results in a "shippment acknowledgment" e-mail automatically being sent to the customer.

The critical differences between 1800 format and 1900 are:

• Format 1800 does not support split shipments (i.e. multiple tracking numbers for orders shipped to the same address).
• Format 1800 does not support multi-address modem (i.e. orders with multiple shipto addresses).

Each order can only be updated once by e-mail. Subsequent e-mailed data for a given order will be ignored. You can manually update the ship status for an order by using the lineitem admin page to modifying the ShipMethod field.

This function is run by a JobQueue job which looks like the example below:

This job is the how the customer sees the results of B2B Post Processing. Make sure that the job is scheduled to run after the cut off time for the outgoing transmittal job.

Notes:

• All incoming e-mails must be ASCII text only (HTML E-Mails will fail).

• The ShipMethod column for each Item used to update the order with the tracking information returned from the fulfillment house. The date shipped is set to the date of the e-mail and set into the requiredShipDate column.

• It is recommened that the return e-mail contains both the name of the carriers and their tracking number combined into the tracking field. i.e. FEDEX TSG6354646345 instead of just TSG6354646345.

• Incoming e-mail is limited to 500 entries per e-mail (anything more will be truncated and lost).

• The record locator can be either the transactionid or the LineItemId. This is defined in param2. In the standard release of SendSafe only the transactionid is supported.

• The subject line in the e-mail must contain the password assigned in param1 of the Job.

EXAMPLE OF INCOMING E-MAIL
From: jj@fulfillmenthouse.com
To: BB@yourbiz.com
Subject: MYPASSWORD
"168552232","UPS 1Z90E13W0343464757"
"284080958","UPS 1Z90E13W0344638933"
"357590726","UPS 1Z90E13W0243506712"
"48604208","UPS 1Z90E13W0343857145"
"62432534","UPS 1Z90E13W0344334127"

FORMAT1900 Shippable Products Mode-A
Transmission of ship instructions

This B2B function is fully integrated with SendSafe and does not require a B2B plugin module. This system will send FORMAT1900 e-mail to the fulfillment house and process a return FORMAT1900 e-mail from the fulfillment house containing order shippment status. This function can also be used in-house as a means of initiating the warehouse stage of product handling.

At a preset time(s) each day, a consolidated list of items which were ordered that day and require fulfillment are automatically e-mailed to the fulfillment house.

FORMAT1900 supports multi-address mode. Orders which have multiple shipto addresses will be result in separate ship instructions generated for each lineitem in the order.

Format1900 supports split shipments (i.e. multiple tracking numbers for orders shipped to the same address). Allocation of a shipping number for each item in an order is defined by the (tracking#)xN format in OrderLineItem.ShipMethod db column.

This function is run by a JobQueue job which looks like the example below:

Format of "Fulfillment Request" outgoing E-Mail

The e-mail which is sent to the fulfillment house is an ASCII email with a comma delimited spreadsheet (*.CSV) attached containing all orders placed up to the cut off time each day. The format of the order header and line item entires depends soley on the configuration of the job.

FORMAT1900 Shippable Products Mode-A
Ship instructions executed message

E-mail is sent from the fufillment house to the e-commerce system to update fulfillment status. This e-mail contains shipment tracking and other information which is automatically imported into the SendSafe database and presented to the customer on their order status pages. The receipt of this e-mail also results in a "shippment acknowledgment" e-mail automatically being sent to the customer.

Each order can only be updated once by e-mail. Subsequent e-mailed data for a given order will be ignored. You can manually update the ship status for an order by using the lineitem admin page to modifying the ShipMethod field.

This function is run by a JobQueue job which looks like the example below:

This job is the how the customer sees the results of B2B Post Processing. Make sure that the job is scheduled to run after the cut off time for the outgoing transmittal job.

Notes:

• All incoming e-mails must be ASCII text or HTML (Content-Type: multipart/mixed) only with one attachment (other formats such as HTML E-Mail (Content-Type: multipart/related) will fail).

• The ShipMethod column for each Item used to update the order with the tracking information returned from the fulfillment house. The date shipped is set to the date of the e-mail and set into the requiredShipDate column.

• Incoming e-mail should be limited to 500 entries per e-mail.

• The record locator is the transactionid + SKU (for line items).

• The subject line in the e-mail must contain the password assigned in param1 of the Job.

• The SQL Selection logic includes orders.storefrontName; as a result, you will need one fulfillment job for each storefront. This provides added flexibility and in handling and format of email responses.

Offsite Digital Products
B2B Payload Fulfillment

This subsystem supports sending an electronic order for product fulfilment and then processing a return e-mail which indicates that the order was fulfilled.

See digital payloads for information on setting up digitally fulfilled items in the database. Please note: that SendSafe can directly handle digital product fulfillment. The only reasons to use an outside company for FulFillment is if you cannot assembled the digital product yourself.

This B2B method uses a plugin module to connect to the fulfillment company. This module can use any type of Internet connection from basic sockets to high level protocols lke http and XML SOAP

Example Record for non-B2B digital payload fullment order:

transactionid	Fulfillment	PostProcStatus
28897	ftp://p1.biz.com/abc/ORDER15647.zip	{COMPLETED};E-RECEIPT PROC:SENT;PAYLOAD

Here the Fulfillment column contains the download link for the payload. The PostProcStatus contains the flag PAYLOAD which indicates that a digital payload was generated for this order.

Offiste Digital Products
B2B E-Mail Relay Acknowledgement

The system will receive e-mails from the fulfillment house. These e-mails will be parsed for an order ID-Key and an acknowledgment e-mail will be sent to the customer who placed the order. These incoming e-mails from the fulfillment house will be processed by a Job in the SendSafe JobQueue as defined below.

Note: all incoming e-mails must be ASCII text only (HTML E-Mails will fail).

Example of incoming e-mail:

Subject: FULFILLMENT RESPONSEMAIL
ThisId: xxxxx
This is your order. It contains:
WXYZ1000
WXYZ2000
Thanks

Example of JobeQueue Entry:

The data that is ID-key in the e-mail is the unique identification code; a transactionId would be fine, but other ID-key codes will work just as well. The ID-key code provided in the e-mail must work with the SQL Select phrase specified in the Job and the E-Mail tagstring (embedded in the SQL statement).

All text on the line following the ID-Key tagstring down through the end of the eimail will be copied into the outgoing e-mail AFTER the Relay Msg (param3).

Offsite Digital Products
B2B Plugin Configuration

Offsite Digital Products
B2B Plugin Module Input

PreProc:

/HOST="203.110.131.25" 
/PORT="80" 
/TIMEOUT=30 
/OPERATIONCODE="PurchaseExtrasWebService/PurchaseExtras.asmx/ValidateExtrasForPurchase" 
/USERID="oesdvalid@oesd.com" 
/PASSWORD="oesd" 
/PARAMLIST="1001-HFBZNNFTVNVH" 
/PAYLOADLIST="W00004" 
/AUDIT="C:\PROJECT\JSOF SSL\jsof\Audit" /FILEOUT="CPROMPT00000004.txt"

PostProc:

/HOST="203.110.131.25" 
/PORT="80" 
/TIMEOUT=30 
/OPERATIONCODE="PurchaseExtrasWebService/PurchaseExtras.asmx/PurchaseExtras" 
/USERID="oesdvalid@oesd.com" 
/PASSWORD="oesd" 
/PARAMLIST="1001-HFBZNNFTVNVH" 
/PAYLOADLIST="W00004" 
/AUDIT="C:\PROJECT\JSOF SSL\jsof\Audit" /FILEOUT="CPROMPT00000004.txt"

Offsite Digital Products
B2B Plugin Module Output

Contents of the results from the file is listed below. This results file is parsed by the e-commerce system and acted on.