Step 4: Check it worked

Goal: confirm the import did what you expected, before you walk away from it.

Five minutes here saves a week of confused emails later.

---

1. Check the count

Open Shopify Orders and filter to the orders just created. The count should match the "Orders To Import" figure EZ Importer showed you. If it is lower, some rows were rejected. The most common cause by far is the trailing apostrophe from Step 2.

2. Check the routing

Open two or three of the new orders and look at the fulfilment section. Each item should have been assigned to a location:

If the order contains	You should see
Tee or hoodie	Ogo Print on Demand
Jersey	Hillbrick
Socks	Office
Ticket	A fulfilment that Guest Manager has already closed

Pick one order that contains several different item types if you can. That proves the split is working, not just the simple cases.

3. Check a ticket actually went out

In Shopify go to Apps, then Event Ticketing, then your event, then Attendees. A buyer who ordered a ticket should now appear there with Source shown as Order. That confirms the ticket email has gone.

4. Update your record

Append the rows you just imported to the running record you keep for Step 2. If you skip this, the next run will re-import everything you just did.

If something looks wrong

Symptom	Most likely cause
Every row rejected, "expected String to be a id"	Trailing apostrophes not stripped
Some items missing from an order	Blank or stale Variant ID in Funraisin for that product, or Excel reformatted the Variant ID column into scientific notation when you saved. Open the file you imported and check the IDs are still full 14-digit numbers
An item went to the wrong fulfiller	Product is missing its collection or tag in Shopify, see Locations and routing
Buyer got two tickets	The order was imported twice
Buyer got a Shopify order confirmation email	Email Customer on Import was left on

More detail on all of these is in Troubleshooting.