Staging Draft preview. Not live. Recipes are not yet tested. Placeholders are marked.
Automate Your Hours

Start here · Lesson 5 of 6

Lesson 5 of 6: An Etsy order log that fills itself in

Not yet tested · planned: mock-tested. Steps and numbers may change after testing.

Full recipe →

Hi there,

So far we've covered listings and stock. Now, orders.

Today: every new order becomes a row in your order log.

If you copy order details into a spreadsheet for your records or planning, this does it for you. When a new order comes in, Make adds one row: order number, status, paid and shipped flags, total, gift flag, and each item's title, SKU and quantity.

You can try it before a real order arrives. Etsy has no test mode for orders, and you can't buy from your own shop. So the recipe includes a separate practice scenario (you test it with Run once and never switch it on) and a sample order file with made-up data shaped like a real Etsy order. Send the sample in, check the row, and delete it. Your live scenario uses the same mapping with Etsy's Watch Shop Receipts trigger, checking every 2 to 6 hours (every 6 hours is cheapest).

One rule we stick to: the log is for you. It has no buyer-email column, and the recipe never emails, texts or adds buyers to a list. If a buyer needs to hear from you, use Etsy's own messages.

What you'll need

  • Make's free plan, the order-log template and the sample order file. Make Free gives you 1,000 credits a month[price-check] and appears to allow only 2 active scenarios, according to a Make community forum report (not a Make pricing or help page). If you plan to run several of these recipes at the same time, that 2-scenario limit could matter. This one needs one switched-on scenario and uses about 210 of 1,000 credits a month checking every 6 hours (estimate, if run alone). Checking every 2 hours instead uses about 450. If you also run the packing sheet from lesson 6 in the same scenario, the two use about 410 together. Make charges 1 credit every time it checks, even when there are no new orders.
  • About 20 minutes for setup (our estimate)

How you'll know it's working
The sample order adds exactly one row that matches the sample file, and the total looks like a normal price. Your first real order adds one row with the same columns.

The three things most likely to trip you up

  1. Totals look 100 times too big. Etsy sends money as an amount plus a divisor. Map amount ÷ divisor.
  2. The practice run adds nothing. The sample didn't reach the webhook or didn't parse. Re-send it and check the webhook's data structure in Make.
  3. The first real order doesn't show up. Check the schedule and reconnect Etsy. The mapping is the same as the practice scenario.

Time saved: about 30 minutes a week, Estimated. That assumes 20 orders a week at about 1.5 minutes each to copy by hand. At 5 orders a week it's closer to 7–8 minutes.

[TEST STATUS: Not yet tested. Replace with "Tested on sample order data; your first real order is the live run. Last tested: {date} (mock-tested)" from the PASS log before this sequence goes live.]

Open the recipe

Next lesson, the last one: a packing list built from your orders, personalization included.

Talk soon, Jesse at Automate Your Hours

Full recipe →