UPS Ground: Ships {{ ship_day }}, arrives {{ arrive_day }}
\nOrder by {{ cutoff_hour }}:{{ cutoff_minute | append: '0' | last: 2 }} CT to ship today.
\nto ship today. Otherwise, ships tomorrow.
\n{{ page.sales_actual | money }}
\nForecast: {{ page.sales_forecast | money }}
\n {% if page.sales_variance > 0 %}\n ↑ {{ page.sales_variance | money }}\n {% elsif page.sales_variance < 0 %}\n ↓ {{ page.sales_variance | money }}\n {% endif %}\n{{ page.backup_events | default: 0 }} fallbacks
\nAvg cost delta: {{ page.backup_cost_delta | money }}
\n{{ page.chat_count | default: 0 }} chats
\nAvg response time: {{ page.chat_response_time }}min
\n{{ page.tax_status }}
\nVariance: {{ page.tax_variance | money }}
\n\n {{ shop.url }}/pages/checkout?ref={{ referral_code }}\n
\n \n {% endif %}\n \nSign in to see your referral rewards.
\n{% endif %}", "note": "Render this on a dedicated page or in account sidebar. The referral code URL param is picked up by your app on the landing page and stored in the cart before checkout." } } ] }, { "url": "https://www.tomsailors.com/b/custom-points-redemption-system", "slug": "custom-points-redemption-system", "title": "Custom Points & Redemption System", "sketch": "I'd build this as a custom app with a Shopify order webhook that fires on payment capture, a theme extension portal for customers to check balances and redeem, and the Discount API to generate codes on demand. The merchant's admin gets a dashboard pulling aggregated points and redemption metrics. It's a straightforward chain: order → points written to metafield → customer redeems via portal → code generated → points deducted.", "problem": "A mid-market direct-to-consumer brand needed to build a proprietary points-based loyalty program where customers accumulate points on purchases and redeem them as discount codes through a self-service portal. The merchant required both a customer-facing interface to track balances and redemption history, and an admin dashboard to monitor program health and customer engagement.", "publishedAt": "2026-05-21T14:25:24.753Z", "updatedAt": "2026-05-21T14:25:24.753Z", "pieces": [ { "position": 1, "name": "Points Accumulator", "category": "Loyalty", "description": "Records points to each customer's account whenever an order is paid, using a multiplier you choose — like 1 point per dollar spent.", "stack": "Custom app + order webhook", "proof": { "kind": "graphql", "language": "GraphQL", "pasteTarget": "Admin GraphQL explorer", "code": "# Admin GraphQL\nmutation SetCustomerPoints($ownerId: ID!, $points: String!) {\n metafieldsSet(metafields: [{\n ownerId: $ownerId\n namespace: \"loyalty\"\n key: \"points_balance\"\n type: \"number_integer\"\n value: $points\n }]) {\n metafields {\n id\n value\n }\n userErrors {\n field\n message\n }\n }\n}\n\n# Variables:\n# {\n# \"ownerId\": \"gid://shopify/Customer/12345\",\n# \"points\": \"150\"\n# }", "note": "Metafield values are always strings. Changed $points variable type from Int! to String! and adjusted the example variable from 150 to \"150\"." } }, { "position": 2, "name": "Customer Portal", "category": "Loyalty", "description": "A dedicated page in your online store where customers log in to see their current points balance, recent earning history, and redemption history.", "stack": "Theme app extension + React", "proof": { "kind": "liquid", "language": "Shopify Liquid", "pasteTarget": "theme/snippets/loyalty-portal.liquid", "code": "{% if customer %}\n{{ points }} points
\n \nEarn {{ 100 | minus: points }} more points to redeem.
\n {% endif %}\nLog in to view your points.
\n{% endif %}", "note": "Include this snippet on a custom page or in the customer account template; the /apps/loyalty/redeem endpoint is handled by the custom app backend." } }, { "position": 3, "name": "Redemption Engine", "category": "Loyalty", "description": "When a customer clicks redeem, creates a discount code pegged to their points spend, deducts the points from their account, and logs the redemption.", "stack": "Custom app backend + Discount API", "proof": { "kind": "graphql", "language": "GraphQL", "pasteTarget": "Admin GraphQL explorer", "code": "# Admin GraphQL\nmutation CreateDiscountCode($input: DiscountCodeAppInput!) {\n discountCodeAppCreate(codeAppDiscount: $input) {\n codeAppDiscount {\n startsAt\n endsAt\n title\n codes(first: 1) {\n edges {\n node {\n code\n }\n }\n }\n }\n userErrors {\n field\n message\n }\n }\n}\n\n# Variables:\n# {\n# \"input\": {\n# \"combinesWith\": {\"shippingDiscounts\": false, \"orderDiscounts\": true},\n# \"startsAt\": \"2024-01-15T00:00:00Z\",\n# \"endsAt\": \"2024-03-15T00:00:00Z\",\n# \"title\": \"POINTS-REDEEM-12345\",\n# \"codes\": [\"POINTS-REDEEM-12345\"],\n# \"customerGets\": {\n# \"value\": {\"amount\": \"50.00\", \"appliesOnEachItem\": false}\n# }\n# }\n# }", "note": "Fixed argument name from 'input' to 'codeAppDiscount', removed unsupported 'id' field, queried only available fields (startsAt, endsAt, title, codes)." } }, { "position": 4, "name": "Loyalty Dashboard", "category": "Operations", "description": "Admin view showing total points issued, redemptions by customer, and top earners — helps you track loyalty health and spot trends.", "stack": "Custom app dashboard", "proof": { "kind": "graphql", "language": "GraphQL", "pasteTarget": "Admin GraphQL explorer", "code": "# Admin GraphQL — fetch customers with points metafield\nquery GetLoyaltyMetrics($first: Int!) {\n customers(first: $first) {\n edges {\n node {\n id\n displayName\n email\n numberOfOrders\n points: metafield(namespace: \"loyalty\", key: \"points_balance\") {\n value\n }\n redemptions: metafield(namespace: \"loyalty\", key: \"redemption_history\") {\n value\n }\n }\n }\n }\n}\n\n# Variables:\n# { \"first\": 50 }\n\n# Note: redemption_history is a JSON string; parse on the app side to compute totals.", "note": "Store redemption history as JSON in loyalty.redemption_history metafield (array of {date, points_spent, code}); query and aggregate in the dashboard." } } ] }, { "url": "https://www.tomsailors.com/b/woocommerce-to-shopify-plus-migration", "slug": "woocommerce-to-shopify-plus-migration", "title": "WooCommerce to Shopify Plus Migration", "sketch": "I'd approach this as a four-phase build: pull the product catalog and inventory via WooCommerce's REST API into Shopify using the Admin GraphQL, store the original WC product IDs as metafield references for traceability; build a URL router that intercepts old paths and serves proper 301 responses to preserve SEO signals; archive the full order history in a queryable Postgres schema outside Shopify (the Admin API has no archive layer); and run an automated pre-launch crawl that validates every redirect and flags breaks before you flip DNS. The merchant gets a clean inventory handoff, zero broken links, and a searchable record of every legacy transaction.", "problem": "A mid-market DTC merchant with eight years of operational history on WooCommerce needed to migrate to Shopify Plus without losing SEO equity, breaking legacy URLs, or severing access to historical order records. The challenge combined technical scope—preserving 301 redirect chains at scale, importing orders with original timestamps, and maintaining inventory accuracy—with the business risk of downtime and organic traffic loss during cutover.", "publishedAt": "2026-05-21T14:23:31.810Z", "updatedAt": "2026-05-21T14:23:31.810Z", "pieces": [ { "position": 1, "name": "Product & Inventory Import", "category": "Migration", "description": "Pulls your product catalog, SKUs, pricing, inventory, and custom fields from the legacy platform into Shopify Plus, storing the original product IDs as reference data so you can trace any discrepancies later.", "stack": "Custom Shopify app + Heroku backend", "proof": { "kind": "graphql", "language": "GraphQL", "pasteTarget": "Admin GraphQL explorer", "code": "# Admin GraphQL — bulk product + metafield import\nquery GetProductsForImport($first: Int!) {\n products(first: $first) {\n edges {\n node {\n id\n title\n handle\n productType\n vendor\n variants(first: 100) {\n edges {\n node {\n id\n sku\n barcode\n price\n inventoryQuantity\n }\n }\n }\n metafields(first: 100, namespace: \"wc_legacy\") {\n edges {\n node {\n id\n namespace\n key\n value\n }\n }\n }\n }\n }\n pageInfo { hasNextPage endCursor }\n }\n}\n\nmutation ImportProduct($input: ProductInput!) {\n productCreate(input: $input) {\n product {\n id\n title\n handle\n }\n userErrors { field message }\n }\n}", "note": "Pair with a CSV or JSON export from the legacy REST API; use metafieldsSet to store original product IDs under a custom namespace for traceability." } }, { "position": 2, "name": "URL Redirect Router", "category": "Migration", "description": "Maps every product, category, and page URL from your legacy platform to its new Shopify equivalent, serving 301 redirects that search engines recognize and preserving all backlink authority.", "stack": "Shopify Plus theme extension + Heroku redirect service", "proof": { "kind": "liquid", "language": "Shopify Liquid", "pasteTarget": "theme/snippets/legacy-redirect-check.liquid", "code": "{% comment %}\n Legacy URL redirect checker — intercept old URLs and 301 them to new Shopify ones.\n Store redirect map in a JSON metafield on the store's settings.\n{% endcomment %}\n\n{% assign legacy_redirects = shop.metafields.migrations.url_map | parse_json %}\n{% assign current_path = request.path | downcase %}\n\n{% for mapping in legacy_redirects %}\n {% if current_path == mapping.old_path %}\n {% comment %} Match found; render 301 redirect {% endcomment %}\n \n \n {% break %}\n {% endif %}\n{% endfor %}", "note": "For true HTTP 301 responses (not meta-refresh), use a Heroku middleware that intercepts requests and returns the proper status code; upload the redirect map as a Shopify metafield CSV." } }, { "position": 3, "name": "Historical Order Archive", "category": "Operations", "description": "Stores your complete order history in a secure, queryable archive with original timestamps and customer data intact, accessible to your team without cluttering Shopify's native order interface.", "stack": "Postgres database + custom admin dashboard", "proof": null }, { "position": 4, "name": "Pre-Launch SEO Audit", "category": "Migration", "description": "Runs an automated crawl of your live legacy site, builds the redirect map, tests every 301 response, and flags broken or missing mappings before you cut over DNS.", "stack": "Crawl service + Heroku validation job", "proof": { "kind": "flow", "language": "text/plain", "pasteTarget": "Shopify Flow editor: When → Then", "code": "Trigger: Manual workflow start or scheduled daily at 2 AM\n\nCondition: Check if \"migration_stage\" metafield equals \"pre_launch\"\n\nActions:\n 1. Send HTTP request to Heroku crawl service:\n POST /crawl/validate-redirects\n Body: { legacy_domain: \"original-site.com\", shopify_domain: \"new-site.myshopify.com\" }\n 2. Wait for response; parse redirect_success_count and redirect_fail_urls\n 3. If redirect_fail_urls.length > 0:\n → Slack notification: \"Redirect audit failed on {{redirect_fail_urls.count}} URLs — review dashboard\"\n 4. If all pass:\n → Email store owner: \"Pre-launch audit passed. Safe to flip DNS.\"", "note": "" } } ] }, { "url": "https://www.tomsailors.com/b/us-canada-split-with-unified-customers", "slug": "us-canada-split-with-unified-customers", "title": "US & Canada Split with Unified Customers", "sketch": "I'd build this as a multi-store sync problem, not a single-store problem. The merchant keeps two Shopify stores (one US, one CA) running in parallel, but stitches them together at three critical moments: on customer login, on inventory adjustment, and at checkout. A background job mirrors new signups and addresses across stores using metafields as link keys. A central inventory sync service pushes the same stock counts to both regions on schedule. A checkout redirect catches customers in the wrong store based on their shipping address and sends them home. All orders flow to one central log via Shopify Flow so fulfillment and email see one unified order stream.", "problem": "A mid-market DTC with a customer base spanning both the US and Canada needed to split into two regional stores while keeping customer records in sync, maintaining inventory parity across locations, and routing customers to the correct store at checkout. The challenge was to avoid duplicate customer accounts, overselling across regions, and fragmented order records.", "publishedAt": "2026-05-21T14:22:55.662Z", "updatedAt": "2026-05-21T14:22:55.662Z", "pieces": [ { "position": 1, "name": "Unified Customer Sync", "category": "B2B / Wholesale", "description": "Keeps one customer record synced across both US and Canadian stores so they stay logged in and their order history is visible everywhere.", "stack": "Custom Shopify app + Storefront API", "proof": { "kind": "graphql", "language": "GraphQL", "pasteTarget": "Admin GraphQL explorer", "code": "# Admin GraphQL - Sync customer to secondary store\nmutation SyncCustomerAcrossStores($input: CustomerInput!) {\n customerUpdate(input: $input) {\n customer {\n id\n email\n firstName\n lastName\n defaultAddress {\n countryCode\n provinceCode\n }\n metafield(namespace: \"sync\", key: \"paired_store_id\") {\n value\n }\n }\n userErrors {\n field\n message\n }\n }\n}\n\n# Use this mutation to apply the same email/name to the paired store\n# and set a metafield linking them\n# Variables:\n# {\n# \"input\": {\n# \"id\": \"gid://shopify/Customer/123456\",\n# \"metafields\": [\n# {\n# \"namespace\": \"sync\",\n# \"key\": \"paired_store_id\",\n# \"type\": \"single_line_text\",\n# \"value\": \"us-store-id\"\n# }\n# ]\n# }\n# }", "note": "Run this on both stores to link paired accounts; a background job watches for new signups and auto-mirrors them to the secondary store." } }, { "position": 2, "name": "Shared Inventory Bridge", "category": "Inventory", "description": "Reads stock from one central source and pushes the same quantities to both stores so products never oversell across regions.", "stack": "Heroku backend + inventory sync service", "proof": { "kind": "graphql", "language": "GraphQL", "pasteTarget": "Admin GraphQL explorer (run once per store location)", "code": "# Admin GraphQL - Adjust inventory on both stores after central sync\nmutation AdjustInventoryBothStores($input: InventoryAdjustQuantitiesInput!) {\n inventoryAdjustQuantities(input: $input) {\n inventoryAdjustmentGroup {\n id\n reason\n changes {\n delta\n quantityAfterChange\n item {\n id\n sku\n }\n location {\n id\n name\n }\n }\n }\n userErrors {\n field\n message\n }\n }\n}\n\n# Call this mutation twice — once for US store locations, once for Canadian\n# Variables example for US location:\n# {\n# \"input\": {\n# \"name\": \"Sync from warehouse\",\n# \"reason\": \"central_stock_source\",\n# \"changes\": [\n# {\n# \"inventoryItemId\": \"gid://shopify/InventoryItem/456\",\n# \"locationId\": \"gid://shopify/Location/us-warehouse\",\n# \"delta\": 42\n# }\n# ]\n# }\n# }", "note": "The backend pulls from your warehouse system on schedule and calls this twice to sync US and CA locations in lockstep." } }, { "position": 3, "name": "Checkout Region Router", "category": "Storefront", "description": "Detects a customer's shipping address at checkout and automatically redirects them to the correct store if they're in the wrong one.", "stack": "Theme app extension + Checkout UI", "proof": { "kind": "liquid", "language": "Shopify Liquid", "pasteTarget": "theme/snippets/region-router.liquid, then include from theme.liquid", "code": "{% comment %}\n Place in theme/snippets/region-router.liquid\n Called from checkout.liquid or cart drawer\n{% endcomment %}\n\n{% if customer %}\n {% assign shipping_country = customer.default_address.country %}\n {% assign current_store_region = shop.metafields.region.code | default: 'us' %}\n \n {% if shipping_country == 'US' and current_store_region == 'ca' %}\nYou're shipping to the US. Redirecting you to our US store...
\n \nYou're shipping to Canada. Redirecting you to our Canadian store...
\n \n\n Subscription Item: \n {% if is_sub == 'true' or is_sub == true %}\n ✓ Yes\n {% else %}\n No\n {% endif %}\n
\n\n ⚠️ We can't mix subscription and one-time purchases above $500 in one order. Please split into separate carts or remove items.\n
\nFirst-Time Customer Exclusive
\n{{ product.description }}
\n