Mail‑in precious metal buying · United States
Money Gold buys precious metal from people who mail it in. One form submit sets off a four-system chain: FedEx returns a shipping label, the customer's account registers itself, and n8n and SMTP carry the updates while the parcel moves. Inside that account the customer watches the video of their own box being opened. Live five weeks from the start of design.
At a glance
The starting point
Money Gold buys precious metal from customers who mail it in from across the United States. The transaction begins with an act of trust that most ecommerce never asks for: the customer puts something valuable in a box and hands it to a courier while no money has changed hands. Every question that follows is about doubt. Did the package arrive. Who opened it. Was that really what was inside. A template site can present those answers as marketing copy. It cannot show them happening. The second problem was operational. Each inbound shipment needs a shipping label, an account for the sender, and a stream of updates as the parcel moves. Done by hand, that is a staff member in a shipping portal for every single lead, and it caps how many customers the business can take.
What we built
The customer describes what they want to sell and submits the form. The FedEx API is called immediately and returns a shipping label. Nobody on the Money Gold side opens a shipping portal, retypes an address, or emails a PDF later that day. Inside the dashboard, a returning customer can generate additional labels the same way for a second or third shipment.
The same submit that produces the label also registers the customer's personal account. There is no separate signup form and no password wall standing between a first-time visitor and the thing they came to do. The account exists because a shipment exists, which suits a business whose first customer action is mailing a package.
n8n runs the workflow behind all of it. As the FedEx delivery status changes, the customer receives email and SMS notifications automatically, with mail sent through a configured SMTP server. The staff side of this is the point: nobody sits watching a tracking page in order to send a reassurance email. The chain runs from form submit through to notification without a person touching it.
Inside the account the customer sees the status of their shipment, the video of their parcel being opened, tools to create new FedEx labels, and their profile settings. The video is the load-bearing part. When a stranger mails something valuable across the country, the open question is what was in the box when it arrived and who says so. A recording of the opening answers it without a phone call.
A Metal API integration is part of the stack, supplying current precious metal rates to the site. Metal prices move during the trading day, and an appraisal quoted against yesterday's number is an argument waiting to happen, so the figure comes from the API instead of from someone updating it by hand.
Design and devices
The sequence set the layout. First the form that produces the shipping label, because requesting the label is the one thing every customer does. Then the account, where the parcel's status, the video of it being opened, a way to start the next shipment, and the customer's own details sit together on one screen. The account is the payoff surface of the whole design, and the priority order on it matches the order a worried person asks their questions in. The design was drawn for this business and built in Elementor on WordPress, so pages stay editable without a developer in the loop. The brief named correct display from smartphones through to desktop as a requirement, and that shaped the layout work as much as the visual direction did. Responsiveness here is practical, phone first. The label form and the status screen are both things a customer reaches for on a phone, one-handed, often while anxious about a package in transit. Form fields, status, and the video player are sized for the small screen first.
What came of it
The outcome we can describe with confidence is operational. A lead that would otherwise require a staff member to open a shipping portal, create a label, set up an account and send an email now runs without anyone's time. The customer gets their label in the minute they asked for it, and the notification chain keeps talking to them while the parcel moves. We are not publishing traffic, ranking or revenue figures here. The SEO work was structural preparation, and we have not been given post-launch analytics to report against. What is verifiable today is on the live site: the page structure, the responsive layouts, and the route into the customer account. Everything past the login screen is described from the build, because it belongs to Money Gold's customers.
Manual steps to issue a shipping labelThe form submit calls the FedEx API directly, and the same submit registers the account. Staff involvement in the label, the account and the notification chain is zero.
Systems running behind one form submitFedEx API for the label, Metal API for rates, SMTP for the mail, n8n running the sequence.
Design start to launchOur delivery time. Covers custom design, the WordPress and Elementor build, the integrations, and the customer dashboard.
The public site is where an assistant does its reading: the page structure is organized around search scenarios, the layouts hold from a phone through to a desktop, and the route into the customer account is in plain sight. Everything past the login screen, the shipment status, the unboxing video, the label generator, is out of a crawler's reach by design, because it belongs to Money Gold's customers. No answer-engine tracking was set up on this project, so this page claims no citation in ChatGPT, Perplexity or AI Overviews. The search work was structural preparation, and its effect has not been measured on our side.
How we ran it
Every project runs on a written plan. This is how this one ran.
We started from the customer's path rather than the sitemap: what they hold in their hand, what they are afraid of, what has to happen in the background at each step. That produced the list of integrations the site would need, which is why the FedEx and account logic sat in scope alongside the design work.
Individual design, then the Elementor build on WordPress. Layouts were checked from small phones up to desktop as pages were built, which the brief named as a requirement. Nothing was left to a theme default.
FedEx API for label generation, n8n for the workflow that ties form submit, account registration and notification together, SMTP for delivery of the mail. Metal API supplies live precious metal rates. This is the phase where the business logic stops being a diagram.
Shipment status, unboxing video, new label creation, profile management. Built as the place a worried customer goes to be reassured, which set the priority order of what appears on the screen first.
Live five weeks after design began, with the automation running end to end: form to label to account to notification chain.
Page structure organized around search scenarios, with a sitemap, so the SEO shape was part of the build rather than a retrofit. We have not been given post-launch analytics to report against, so the search work is described here as structural preparation, and its effect has not been measured on our side.
Straight answers
Yours is probably close to one of these. If not, ask it directly.
Ask about your projectSame team, same method
Tell us what you sell and where you sell it. You get a plan like the one above, with the first step priced out and dated before anything starts.
