Urgent.News

What's breaking now, across thousands of outlets.

Tech

I replaced a brand's Shopify app stack with code. Here's what it really costs

The usual Shopify answer to "can the store do X?" is "there's an app for that". Install it, pay monthly, live with its widget, its script weight and its idea of how your store should look. For a publisher I run tech for ( 4 stores, 4 countries, 4 currencies ), I stopped saying that. Most of what would normally be an app is now code we own. AI didn't write it for me, but it made one engineer fast…

In place of relying on third-party Shopify apps, a publisher's 4-stores, 4-countries, 4-currencies store has transitioned to building its own code-based solutions. Rather than simply installing apps for each desired function, the team opted to create code that directly meets their specific needs. This approach allows them to have full control over their systems, eliminating the reliance on app vendors for bug fixes and updates.

Key features built from scratch include a Frequently Bought Together bundle builder, a guided quiz that creates personalized book libraries, a cart upsell system, and an AI shopping assistant. By owning the code, the brand has eliminated limitations imposed by app-based solutions, such as a 25-discount cap and the inability to hide cash on delivery when customers opt-in.

The shift to custom code has also enabled the store to maintain a cleaner, more cohesive design, with no visible app components. While owning the code comes with the responsibility of debugging and maintaining the systems, for a multi-store brand with unique business rules, this investment in code-based solutions pays off in the long run.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Why Naive Text Extraction Destroys RAG on Multi-Column PDFs (and How to Fix Reading Order)

When an AI retrieval-augmented generation (RAG) pipeline hallucinates on a question sourced from a scientific paper or financial report, the debugging process almost invariably looks at the wrong…

  • Naive extraction breaks reading order in multi-column PDFs
  • Multi-column braiding problem causes semantic mix of topics
  • Tiered approach fixes reading order using geometric and vision models

Boundary change, not version bump

The WASI Subgroup voted to ratify WASI 0.3.0, and the change sitting under the version number is that stream<T> , future<T> , and async are now first-class constructs in the WebAssembly Component…

  • WASI 0.3.0 ratified with major changes to WebAssembly Component Model
  • Stream T, future T, and async now first-class constructs across components
  • WASI 0.3 introduces completion-based behavior closer to Linux iouring

Why Filled PDF Forms Open Blank in Some Viewers (and How to Fix It)

If you build document workflows, web upload portals, or automated billing pipelines, you have likely run into this frustrating bug: a user fills out a PDF form, submits it, but when an administrator…

  • PDF forms have separate Field Dictionary and Widget Annotation layers
  • Blank boxes occur when values written without valid appearance streams
  • Form flattening converts interactive PDFs to static content streams

More from Saturday 7 November →