An Insured Shipping Platform on the FedEx API, Live in Four Months
A shipping and package-insurance business with everything but a system. Four months later: accounts, rates, FedEx labels, tracking, invoices, claims and reporting on one platform they own.
- Systems Shipped
- 50+
- Client Retention
- 98%
- Uptime
- 99%
- Engineers & Designers
- 40+

The Obstacle
The client runs a shipping and package-insurance service for businesses. A company that would rather not deal with FedEx directly signs up with them, ships on the rates the client sets for it, and can insure what it ships; many of those shipments are worth $50,000 to $200,000. The client had the FedEx relationship, the rates, the insurance product and the customers. What they didn't have was a system.
Everything a platform would normally do was being done by hand: approving a new customer, setting that customer's rates, creating labels, tracking shipments, raising invoices, handling a claim, and assembling the reports the owner wanted every week. It worked because the CEO carried it, and it could not grow faster than he could.
They needed one platform with two sides: one where customers ship, insure, pay and run their own staff, and one where the client's team approves accounts, sets prices, reviews claims and bills. And they needed it in months, because the business was already running without it.
Discovery: A Client Who Knew What He Wanted
Some discoveries are archaeology. This one was dictation. The CEO knew his business dot to dot: how a new customer is approved, how rates are set for each account, how a label is created and billed, how a claim is reviewed, what he needs to see on a Monday morning. He had been running it; he just had no system to run it on.
Our job in discovery was to write it down precisely, ask the questions that exposed the edge cases (a customer who wants insurance but ships elsewhere; an employee who may create labels but must never see billing; a claim where FedEx's status and the customer's account of events disagree), and then not change it. Nothing in the first design had to be revised after build. That is rare, and it is what happens when the person describing the process is the person who runs it.
It was also a brand-new system, so there was nothing to migrate and nothing old to keep alive while the platform took over. The one thing we did push back on was the monitoring team, and that became a second system (below).
What We Built
- The customer side. A business signs up and, once approved, ships from one dashboard: FedEx labels for domestic and international packages at the rates set for its account, live tracking, invoices to pay and shipping reports. It insures a shipment as it ships and files a claim from the same account if a package is lost or damaged. The owner adds employees and decides what each may do, such as creating labels or viewing billing.
- The admin side. The client's staff approve new customers, set each account's prices, review insurance claims and manage billing for every account from one place. It is the system the business is run on, and the reporting the CEO used to assemble by hand comes out of it.
- A customer can sign up for shipping only, insurance only, or both. The platform runs on the client's infrastructure, under their credentials, with the code and the data theirs from the first commit. It went live in four months.
What the Platform Does Day to Day
A new business applies; the client's team approves the account and sets its rates. From then on the customer creates its own FedEx labels through the API, domestic or international, insures the shipments it wants covered, and watches them move. Invoices are generated by the platform and paid through it. When a package is lost or damaged, the claim is filed from the customer's account and lands in the admin queue for review. Admin sees every account, every live shipment, every open claim and the billing behind all of them, and the CEO sees the numbers he asked for in discovery, which were the numbers he had been assembling by hand.
What the Client Owns
The platform is deployed on the client's own infrastructure under their credentials. The source code, the data and the documentation were theirs from the first commit, and there are no per-seat fees as their customer base or their team grows. If the relationship ended tomorrow, the platform would keep approving, labeling, insuring and invoicing.
What Came Next
The platform runs the business. Watching the shipments is a different job, and when the client asked for a team of people to do it, we built a second, separate system instead: an automation on n8n that tracks every shipment through the FedEx Tracking API, flags any that go quiet for four hours and escalates at 24. It now monitors more than 2,000 shipments a day and takes one person about ten minutes at the end of each day.
The two are separate systems. The platform is the system of record for accounts, shipments, insurance and billing; the monitoring is a workflow that reads shipment reports and tracking data and keeps its own log. Each can change without touching the other.
What Changed
- A business that had been run by hand now runs on its own platform, deployed on its own infrastructure, live in four months
- Customers create their own FedEx labels, domestic and international, insure their own shipments and file their own claims
- Each customer decides which of its employees may create labels and which may see billing
- The client's team approves, prices, reviews claims and bills every account from one admin side
- The reporting the CEO used to assemble by hand comes out of the system
What We'd Tell Another Founder
When the owner can describe the process dot to dot, the most valuable thing a vendor can do is write it down accurately and build exactly that. Some projects need the floor walk; this one needed a careful listener and a team that didn't improvise.
Build the system of record first and keep it clean. The jobs around it, like watching the shipments, are better done by small separate systems that can change every month than by bolting them onto the platform.
TechCentera delivered our platform on time. The speed, the UI, the workflow, the system design, the security — I've been satisfied with every part of it.
Tell Us How Your Operation Runs.
We'll Tell You What to Build.
A free 30-minute consultation with our founder. You leave with a clear view of what to build, what to automate and what to leave alone. No pitch deck. It is the shortest way to find out whether we are the right custom software development company for your operation, and we'll say so either way.
Book a Free ConsultationFive initial discovery calls a week, one a day, 11 AM to 3 PM Eastern.