Sat down and redesigned tacey.app 🚀🚀 After pivotinga little bit to the @Shopify thank you and order status page. The site was just harder to read than the app. Cleaned the story, updated the pages! Easy order editing, address validation, upsells right there on the thank you page

Shopify CLI can create and delete dev stores now. Also a hard 250-store cap per org. Ghost test stores used to pile up forever. Cleanup is a script now, not a weekend chore. shopify.dev/changelog/create… #ShopifyDev

Paid. Then the customer texts wrong size. Hold fulfillment before packing starts. apps.shopify.com/tacey #Shopify #ecommerce

I think Shopify apps bury the daily action three menus deep. Put what merchants do every day on the home screen. Settings can wait one click. #ShopifyDev

Shopify cut Events subscription query complexity from 250 to 100 points. Classic webhooks untouched. If your handler still pulls the whole product plus a pile of variants on every price tweak, that subscription is about to break. Split by trigger. Query the changed variant, not the catalog. shopify.dev/changelog/events… #ShopifyDev

Same customer, two orders, a few minutes apart. Merge them before fulfillment instead of shipping twice. apps.shopify.com/tacey #ShopifyDev

I think most Shopify apps ask for too many permissions on day one. Trust first, scopes later.

Shopify just made variants hold multiple barcodes instead of one. Same SKU can carry a manufacturer UPC, a private-label EAN, a GTIN, an ISBN, even an ASIN, up to 20, with typed validation if you declare the standard. The old single barcode field still works but it is deprecated, and apps that only read that field will silently miss every extra code once you add a second one. If you sync to an ERP, marketplace, POS, or supplier feed, move to the new barcodes connection before that gets ugly. shopify.dev/changelog/produc…

builders, what's the smallest change that got the biggest thank-you from a user?

wrong apartment number shouldn't open a support chat. let them fix the address on thank-you or order status, then packing moves. apps.shopify.com/tacey

When do you kill a half-built feature instead of finishing it?

logged which Shopify webhooks I skip and why. next sync scare starts from a list, not a guess.

builders: do you add a settings toggle for every feature, or pick a default and ship?

Paid is not packed. A short hold after checkout buys you edits without burning the sale. #ShopifyDev

Most order edits should happen before packing starts, not in a support inbox. Let the customer fix a typo on the thank-you or order-status page, then let fulfillment move on. apps.shopify.com/tacey

builders: do you keep a public changelog, or just ship and let people notice?

shipped three tiny fixes this week that nobody will notice except the person who stopped emailing support. those are my favorite kind.

shipped another boring Shopify fix: hold fulfillment when the address smells wrong. they fix it themselves. packing waits. apps.shopify.com/tacey

builders: do you ship ugly and fix later or polish first

shipped a tiny Actorly fix at 6am. staff change history finally shows who restored what. boring. useful.

Been expecting this. Nice move