ShipRush SQL: Introduction

ShipRush SQL allows ShipRush to tie to any standard database (such as Access, SQL Server, MySQL, etc.) using simple SQL queries via an ADO data source.

Why to use ShipRush SQL:

You want ShipRush tied to a system not natively supported by ShipRush
You need ShipRush to work differently with a system that is supported by ShipRush
You want to use a bar code scanner to read an order number (or customer ID, or whatever) and to pop up ShipRush

Examples of ShipRush SQL:

Tie ShipRush to a custom Access order management database
Use ShipRush with Great Plains, but put ShipRush out in the warehouse where Great Plains is not running
Packing lists are printed with a bar coded order number. ShipRush in the warehouse should drive from the bar code, not from an accounting system.

Steps to use ShipRush SQL:

Review ShipRush SQL Videos: Northwind Great Plains
Review this documentation
Experiment with the ShipRush ADO Example Scripts (examples for Solomon, GP, Northwind and ASPDotNetStorefront)
Write the SQL queries to fetch and write the ShipRush data to your database
Test the queries in ShipRush
Go live!

Needed Parts to use ShipRush ADO:

Database that can be accessed by SQL Queries through an ADO driver (Access, SQL Server, Oracle, MySQL, and most others)
Someone to write the SQL Queries. (Z-Firm can refer you to a consultant if you do not have this expertise on tap)
ShipRush SQL (you can develop using the ShipRush demo, if that is convenient)
A few hours to put the pieces together

Familiarity with the database and comfort with simple SQL statements is required to set up ShipRush SQL, but is not needed to use ShipRush SQL for shipping.

Z-Firm Technical Support is not able to assist with SQL query development. Z-Firm Customer Service can refer you to a consultant if you need assistance developing your queries.