order-fetcher v3.2.0

order-fetcher

Retrieves WooComerce order information and displays it in your terminal or saves it as a CSV file.

Getting started

After installing order-fetcher (via npm install -g order-fetcher), you can run orders config init to create your initial configuration file. It will ask a bunch of questions to help get everything set up. You will need to make sure that the WooCommerce API is enabled, and that you have a key and secret defined. Because order-fetcher only ever retrieves data, and never makes changes to your site, it only requires read-only access.

The nickname you give your site allows you to disambiguate if you have more than one: orders host1 ... and orders host2 ... will retrieve data from either “host1” or “host2”, assuming those are the nicknames you gave. (But please, for your own sanity, use useful and memorable nicknames!)

If you don’t have too many historical orders on your site, your first request can be as simple as orders host1. If you have a lot of orders, however, that command can take a while. Using the --after option to only include orders on-or-after a particular date (like orders host1 --after 2019-07-01) can dramatically improve performance.

Usage

As of v1.0, order-fetcher now also installs as the command orders, and uses a more “subcommand”-style command-line (like git, npm, and other tools). It also uses the host nicknames (as defined above, in Getting Started) as subcommand shortcuts rather than the older and more-verbose --host hostname flag. Note that you can still use orders get --host host1 ... rather than orders host1 ..., but you’ll find that the newer second invocation is more natural and involves less typing.

When all else fails, orders --help (or order-fetcher --help) lists all of the available options.

Top-level commands/options

config commands/options

get (or host-nickname) options

Best practices

For WooCommerce installations with a large number of historical orders, making use of the --after options is highly recommended. Similarly, use --status processing to only include orders that haven't been handled yet. (And then mark those orders as "completed" as soon as you deal with them.)

When generating CSV output, the columns come directly from the item information in WooCommerce. More than likely, you'll want to use the --sku option to create CSV files on a sku-by-sku basis.

About column filtering

The various --omit... and --include options control whether columns are included or omitted in the output. As a rule of thumb, columns are included for CSV file output for consistency across invocations, and the --omit-... options are enabled by default for screen output to reduce line-wrapping. If you need to not omit columns for screen output, you can prefixthe option with no, as in --no-omit-identical.

If the --omit-... options are too coarse, you can enable or disable individual columns using the --include and --omit options, or for complete control use the --columns option to specify exactly what columns you want displayed and in what order they will appear. Using --list-columns will list all of the column names available. Do note that unless you use --columns to specify an exact set, the following columns are always included: "order#", "date", "name", "email", "qty", and "total".

Examples

orders host1 --after 2019-01-01 --status processing --list-skus

Retrieve all orders after 1 January 2019 (inclusive) with a status of "processing", and list the unique SKUs. This is useful as a precursor to creating per-SKU CSV files.

orders host1 --after 2019-01-01 --status processing --sku some-sku --out some-sku.csv

Retrieve all orders as in the previous command, filter the items to the SKU 'some-sku', and write to 'some-sku.csv'.