Next.js front-end with Sanity CMS and live ERP integration for an industrial component manufacturer.
Stack
The Problem
An industrial component manufacturer had a corporate website built six years earlier on a platform nobody on their current team could update. The product catalog was managed in spreadsheets shared by email. Sales teams were directing customers to pages showing discontinued products and incorrect specifications. The content management system required developer involvement for any update, and the developer who had built the original site was no longer with the company.
The Result
Operations team manages all content independently. Product catalog is accurate and live. Product pages are indexed in search for the first time in the company's history. The sales team now directs customers to product URLs with confidence.
What we built
Approach
Content is authored in Sanity Studio and served through Sanity's CDN. The Next.js application fetches structured content at build time for static pages and uses Incremental Static Regeneration (ISR) for product pages, which revalidate every 15 minutes. When an author publishes in Sanity, a webhook triggers the Vercel revalidation API, updating affected pages immediately. Product availability is fetched from the ERP REST API at page request time (not build time) to ensure live stock status. Algolia search is updated via a Sanity event listener that pushes new and modified products to the search index on publish. The Cloudflare layer provides DDoS protection, caches static assets, and handles the domain.
Full technical report
The full write-up includes architecture diagrams, technology selection rationale, implementation phases, and lessons learned. Available for qualified enquiries.