Case Study
Surplus Containers
Surplus Containers needed a lean public inventory and contact surface that could run on shared hosting while supporting a private operational campaign workflow behind it.
JAMARQ built a public React/PHP site with inventory preview controls, contact intake, crawler-safe SEO basics, and a separate authenticated admin workspace for campaigns and inventory operations.
The public case study intentionally excludes campaign records, contact lists, private inventory rows, and admin screenshots; confidential workflow details are summarized only.
Public Inventory Surface With Private Operations Behind It
Surplus Containers is not just a landing page. The public site supports inventory visibility and contact intake, while private campaign and inventory operations stay behind authentication. The public case study documents the shareable surface without exposing operational records.
Business type
Shipping container availability and sales
Public surface
Inventory preview, contact intake, legal pages, sitemap, robots
Private surface
Authenticated admin workflow omitted from public screenshots
Stack
React, Vite, PHP API, MySQL, SendGrid
Screenshots
Public Proof, Confidential Records Omitted
Screenshots show only public pages and masked inventory proof. Admin campaign data, contact lists, private rows, and credentials are intentionally excluded.
Current live Lighthouse/PageSpeed evidence for the production public site.
Current live Lighthouse/PageSpeed evidence captured June 3, 2026: 100 desktop performance, 96 mobile performance, and 100 accessibility, best-practices, and SEO scores.
Technical note
Measured locally with Lighthouse against the live production URL. Scores can vary by network and runtime conditions.
The Challenge
- •The public site needed to communicate availability without exposing private customer or campaign data.
- •The operator needed a predictable way to handle inventory-driven contact and campaign workflows on shared hosting.
- •The deploy package needed to keep public files, admin files, backend routes, and production environment handling separate.
- •SEO and crawler rules needed to index the public site while keeping admin and API surfaces out of public search.
The Solution
- •Built separate public and admin React apps so the customer-facing route stays small and the operator tools stay authenticated.
- •Added a public inventory preview with access-token-aware copy and a contact path for full inventory requests.
- •Kept private campaign, contact, inventory, and delivery-tracking workflows out of public screenshots and case-study assets.
- •Added cPanel deploy packaging, archive checks, branded error pages, sitemap, robots, and route verification.
- •Kept server-side guardrails for campaign caps, kill switches, validation, and delivery tracking.
The Result
Want the private operational walkthrough?
A deeper walkthrough can cover campaign, contact, inventory, and delivery workflows privately. Those records are not published in this public case study.