Importing sales data

budgetkids

Currently, we have information on our store pages such as quantity of orders, turnover, and other sales information.

I propose a way to download the information in a format that is used by a database such as Microsoft Access.
A store can use this information for MANY purposes such as statistics over time, location of sales, areas of opportunity, and for so much more.

Example, I use Access 2013 to organize my survey results (I give out a survey with every order). Also a question in this survey I ask if they would like to be contacted in the future with deals, coupons, etc. This would be easier to track and use if I had both sales data, survey results, history of coupons all on one customer. This way we can customize better solutions and more effective coupons. (Some may prefer free shipping while other purchase a large amount and prefer a percentage off)

Access can import an Excel file, a Delimited text file, or in a database format such as .accdb extension.


Thank you,
Chris

Lawrence

Quantity of orders and turnover could be taken from the order download file, or the api will give you more detailed data like location of customer, but likely both of these would require work on your part to get it into something Access is happy with.

Stragus

I know nothing of Access or Excel (or Microsoft software in general), but I could add some command in BrickSync to output tab-delimited lists of orders, for both marketplaces, without too much trouble...

Anyone else would find that useful? (to help decide where to put that in my spare time to-do list)

Bricks.without.Mortar

^+1

minithingsforlife

@Stragus
Yes would definitely find this useful

Stragus

I have started working on this little feature.

@Lawrence, can we get the username in /order/view? We get the customer's real name, but I suspect that's far less convenient for sending coupons and such.

Stragus

Done! That was a little more work than I expected, but here's the new "saveorderlist" command with BrickSync 1.5.3:


For BrickOwl orders, it saves the customer's full name since I apparently can't get the username from the API ( @Lawrence, a little hand?).

The information is limited by what's accessible with the BL "order list" API call. Querying more information would require an API call per order, and a big seller would then risk running into their daily 5000 BL API limit.

BrickSync 1.5.3 now also saves order information in the BSX files of received orders, as a new XML block. Future features or software will probably use that information.

I hope the new feature is appreciated!

budgetkids

@Stragus THANK YOU!