Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallYes—if the catalog changes infrequently and customers can confirm shipping, installation, and final order details in a conversation. A reported Next.js 16 case study describes a 250-product catalog built from repository-held data, with one SKU-keyed price file and a cart that hands off to WhatsApp instead of taking payment. That arrangement can keep catalog prices centralized without creating a database, but each published catalog change still requires a build and deployment, and the business must handle inquiries and confirm orders manually.
What a database-free catalog looks like
The case study describes a Turkish seller of outdoor LED decorations, including pole motifs, illuminated figures, arches, hanging ornaments, and LED sold by the metre. Its author reports 250 products across 32 categories and 750 SKUs, including 37 products with a single variant. These are figures reported by the case-study author, not independently audited measurements. Read the case study on DEV Community.
As an Amazon Associate I earn from qualifying purchases.
The reported design separates catalog content, prices, and each shopper’s cart:
- Catalog content: JSON files under
data/catalog/hold product information, with a shared typed module providing access to that data. - Prices:
data/fiyatlar.jsonmaps SKUs to net prices. The article says VAT-inclusive display figures are calculated from net prices during the build. - Cart: Each customer’s browser stores selected items and quantities, rather than a server-side order record.
In this model, a database is not needed to serve the catalog pages or remember a cart on one browser. The trade-off is that the repository is the editing workflow: changing a product or price means updating the data and rebuilding and redeploying the site.
#1 Best Overall
How one price JSON file stays in sync with the cart
The case study reports that the cart, stored in browser localStorage under the key ls_cart_v1, contains a SKU and quantity for each line, with optional metres or a note where applicable. It deliberately does not store prices. When the cart is rendered, the site looks up the current price for each SKU in the price data.
That separation helps avoid displaying an old price simply because a shopper’s cart was created before the price file changed. It is not a price lock: the site must first be rebuilt and deployed for the new file to become published, and the displayed total does not reserve inventory or guarantee that the seller will accept the order at that amount.
Rank #2
Because localStorage exists in the browser, code that reads it must run client-side rather than during server prerendering. The Next.js static-export guide documents this browser-only constraint for Web APIs such as localStorage. Next.js static exports guide.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What static export in Next.js 16 provides—and excludes
The Next.js guide, labeled version 16.3.8 and updated August 25, 2026, says that setting output: 'export' makes next build generate HTML for routes and place the output in an out directory for a compatible static web server to host. Server Components run at build time; the guide also supports static GET route handlers in this mode.
Static export is a good fit when the site’s published content can be prepared at build time. It does not provide request-time server behavior for features that depend on live requests or server-side state. The guide lists request-dependent route handlers, cookies, Server Actions, and Incremental Static Regeneration (ISR) among unsupported features in this deployment mode.
Consequently, this architecture does not by itself supply real-time stock, payment processing, per-customer server state, or an authoritative server-side order record. Adding those capabilities means introducing a server-backed component or using a commerce platform that provides them.
How the WhatsApp cart handoff works
WhatsApp click-to-chat links open a conversation using a phone number in full international format, written without a plus sign, brackets, or dashes. A ?text= parameter can prefill URL-encoded message content; the customer still needs to send that message. WhatsApp Help Center: How to use click to chat.
According to the case-study author, a product inquiry includes the name, SKU, selected choice, quantity, shown VAT-inclusive price, and a prompt for the customer’s delivery city and district. The cart message is shortened when its encoded text exceeds a project-set threshold of 1,800 characters. That number is the project’s implementation choice, not an official WhatsApp message limit. The reported compact message preserves SKUs, quantities, and line totals and adds a shareable cart link.
This is an inquiry and order handoff, not checkout. The case study says shipping and installation are quoted separately, so staff must respond, confirm the final quote and order details, and complete the sale through the business’s own process. Neither a prefilled message nor a displayed cart total charges the customer or confirms stock.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When this design is a fit—and when it is not
| Question | Static catalog and WhatsApp handoff | Server-backed store or commerce platform |
|---|---|---|
| How do catalog edits go live? | After a data change is built and deployed. | Runtime editing may be available; exact behavior depends on the chosen system. |
| How certain is the transaction at cart time? | The customer requests a quote; final shipping, installation, and order terms are confirmed in conversation. | A checkout can collect shipping, taxes, and payment, subject to the platform’s configuration. |
| What order work remains manual? | Someone answers the message and confirms the order and final price. | Order handling can be automated to the extent supported and configured by the system. |
| What data does the approach suit? | Relatively stable catalog content and prices that can be published through deployments. | Persistent stock, customer, or order state that needs server-side management. |
A no-database setup is most compelling when catalog updates are occasional, product information is predictable, and a human quote is already part of the sale. It becomes less suitable as soon as the business needs live inventory, payment, automated order processing, or records that must persist centrally. Those needs are not reasons to add complexity preemptively; they are signs that the static model’s operating assumptions have changed.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
