The Data Export tool allows ezStore123/MerchantComplete data to be exported for various integration purposes. 
Data from the tables listed below can be readily exported to several file formats.

Note: To make sure you export all records, set the date range to cover all possible records (example: 1/1/1900 thru 1/1/2100).

Order Export Strategy:
The system makes no assumption about the order data exported and allows export of orders of any status, even orders with errors or incomplete orders.
This allows merchants to use exported order data for data mining purposes if needed.
When exporting orders with the intent to upload them to an accounting system or an external order manager system, we recommend the following approach in order to prevent order export duplication or other issues:
- Print an order report for all new orders from the previous day.
- Post the new orders from the previous day.
- Export the posted orders from the previous day.
This method guarantees accuracy. No overlapping effect or duplication discrepancy may occur between actual order data and exported data.
By the same logic, it is not recommended to export new orders for the current day since more orders may be added before the current day ends. 

Exporting posted orders from the current day:
If you post and export new orders more than once a day, exports will contain duplicate information since the system will always output all posted orders.
You may repeatedly post and export orders for the current day if your accounting system or order manager is set up to recognize and ignore duplicate orders. 
This method should be used only if your company requires an unusually fast order turn-around rate.

The following export formats are supported:

• Delimited file using tab or comma as delimiter (.TXT). This is the default export format. It is compatible with Microsoft Excel and Access import formats.
• XML file (.XML). The generated XML files can be parsed by any XML parser (V1.x or higher). 
  
  The file layout is as follows ('TABLENAME' is replaced by the actual table name):
  
  <object name="TABLENAME">
      <TABLENAME>
          <columnName>data</columnName>
          ...
      </TABLENAME>
      ...
  </object>
  
  When exporting orders, the generated XML also includes order detail information. Example:
  <order>
  order data...
    <detail>
    detail data...
    </detail>
  ...
  </order>
  
• Mail Order Manager: The order data can be exported to Mail Order Manager format. M.O.M. integration may require system customization. Please contact  //digital things for M.O.M. integration.

After the export process is complete, a link to the export file will appear at the bottom of the screen. 
- If you selected 'Tab-delimited' format, either right-click and 'Save As' or click on the link to download the file (xxxx.TXT). You may be prompted for user name and password for security purposes.
- If you selected  the 'XML' format, right-click and 'Save As' to download the file (xxxx.XML). You may be prompted for user name and password for security purposes. Clicking on the link will load the XML file into your browser. Choose this method only if you just want to look at the data.
- If you selected  the 'M.O.M.' format, right-click and 'Save As' to download the file (order.MOM). You may be prompted for user name and password for security purposes. Clicking on the link will load the MOM file into your browser. Choose this method only if you just want to look at the data.

Notes:
1. Data contained in the export file may be highly confidential. Make sure all transfers are executed via a secure channel.
2. Delimited files can be read by most applications such as Access, Excel, etc... The exported data file can be imported directly into a SQL server using the BCP utility (specify the -c switch).  When importing to Excel or Access, make sure that text fields containing large numbers are imported as text otherwise the target application may attempt to convert them to very large number format with power notation (ex: 5454545454545454 will become 54E15, which converted back to text will be 5454545454545450 instead of its original value).
3. XML files are 'DTD-less'. They can be processed with any XML engine (XML 1.0 specification or higher).
4. Previous export files are overwritten each time the utility is used.
5. When exporting orders in text format, 2 files are generated: Order.txt and OrderDetail.txt, containing respectively the order and detail information. XML exports include the detail information as illustrated above.

Security Tip: After extracting the desired data, run an export for which you are sure no data can exist (for example date range in the future). This overwrites any previous data on the server with an empty file header and insures data security.