Case Study
Surplus Containers
Surplus Containers needed a lean inventory and contact site that could run on shared hosting while keeping campaign work secure behind it.
I built a public React/PHP site with inventory previews, customer contact forms, search-friendly pages, and a separate secure owner workspace for campaigns and inventory.
The public case study excludes campaign records, contact lists, private inventory rows, and owner-tool screenshots; confidential business details are summarized only.
Public Inventory With Secure Operations Behind It
Surplus Containers is not just a landing page. The public site supports inventory visibility and contact requests, while campaign and inventory work stays behind authentication. The case study shows the customer experience without exposing confidential records.
Business type
Shipping container availability and sales
Customer-facing site
Inventory preview, contact form, legal pages, sitemap, robots
Owner tools
Secure management tools omitted from public screenshots
Stack
React, Vite, PHP API, MySQL, SendGrid
Screenshots
Public Proof, Confidential Records Omitted
Screenshots show only customer-facing pages and masked inventory examples. 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 owner needed a predictable way to handle inventory inquiries and campaigns on shared hosting.
- •The deploy package needed to keep public files, admin files, backend routes, and production environment handling separate.
- •Search engines needed to index the public pages while keeping private owner tools out of search results.
The Solution
- •Built separate customer-facing and owner-facing React apps so the public site stays small and the management tools stay secure.
- •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 records out of public screenshots and case-study assets.
- •Added cPanel deploy packaging, archive checks, branded error pages, sitemap, robots, and page verification.
- •Kept server-side guardrails for campaign caps, kill switches, validation, and delivery tracking.
The Result
Want a private owner-tools walkthrough?
A deeper walkthrough can cover campaign, customer contact, inventory, and delivery tools privately. Those records are not shown in this public case study.