A shipment status screen exists so a tracking call has an answer on your side. Sales stops waiting on the warehouse or refreshing a carrier page with the customer still on the line. Release one keeps where the order is as a single record.
Four statuses
Preparing, left the building, exception, delivered. If your words differ, you write the list. A long list is how the warehouse abandons the screen. An exception carries a short note: address, missing line, hold.
Who may change it
Warehouse or dispatch changes the status. Sales reads it and does not invent a time. Two roles cannot stamp two different hours. HED Creative asks who actually knows the status today. That name is settled in discovery, from Berlin or Ankara.
A carrier integration is not a condition of release one. A tracking number can be typed. It sits on the order. Any message to the customer is read from that record.
What the customer sees
Release one is an internal screen. Sales answers the call from it. A customer login is a portal decision of its own. Margin, internal notes and another customer order stay inside.
One record of the hour
Wherever the order is opened, the status is written there or read from there. Two places do not keep two clocks. The screen is not a copy of the carrier site. The date you promised and the date it left sit side by side.
Set the scope on web app development. If the chain starts with a visit, see the technician work order. The team that keeps the status after launch is a software partner.