Everything SelfServe does, and the setting behind each of it

The validator does four things in sequence. It parses the address into its component parts, so a house number typed into the city field is recognised for what it is. It compares the street, locality and postal code against the postal authority record for that country, so a real street in the wrong town is rejected rather than accepted. It normalises formatting to the local convention, which means abbreviations, casing and the order of lines come out the way the carrier expects them. And it flags the classes of problem that a human would spot: a missing sub-premise on a large apartment building, a PO box submitted where the shipping profile does not allow one, a postal code that belongs to a different region than the city named above it.

When the address resolves cleanly, the customer sees a confirmation and the corrected version is saved. When it resolves to something close but not identical, the customer is shown the suggested version beside their own and picks one, so you are never silently overwriting what somebody typed. When it does not resolve at all, the save is blocked with a plain-language explanation, and the customer either corrects it or is handed a link to contact you.

The point is timing. An address caught at this moment costs nothing. The same address caught after the label prints costs a return-to-sender fee, a second outbound shipment, a support conversation, and usually the goodwill of somebody who has already paid you.

The window is a single setting with three presets, and it starts counting from the moment the order is created. One hour suits stores that pick and pack continuously through the day and cannot afford a moving target. Three hours is the common choice for stores with a same-day cut-off, since it covers the gap between an order being placed and a picker touching it. Twenty-four hours works for made-to-order and pre-order stores, where nothing physical happens on the first day anyway.

The customer always sees exactly how much time is left. The Order Status page shows a live countdown next to the edit button, so nobody has to guess whether they are still allowed to act. When the timer reaches zero the controls disappear rather than failing on submit, which is the difference between a clear boundary and a frustrating one.

SelfServe also respects what has already happened to the order. If a fulfilment is created, or the order is marked as being picked, the window closes early regardless of how much time was nominally left. A configurable time limit is a promise to the customer; the fulfilment check is what keeps that promise honest against your warehouse.

Each change type is its own setting: email, phone, recipient name, delivery address, delivery instructions, and product additions. Turn on the ones you want. A store that ships internationally might allow contact edits everywhere but refuse address changes that cross a country border, since that would invalidate the duties already calculated at checkout. A store with a single fulfilment run each morning might allow everything, but only for the three hours before that run starts.

On top of the per-type switches there are guard rails on frequency and scope. You can cap how many times a single order may be edited, which stops one indecisive customer generating a dozen change events on the same record. You can require that address changes stay within the original country, or within the original shipping zone, so the rate the customer paid still matches what you are being asked to ship. And you can exclude orders that carry particular tags, which is the usual way to protect wholesale, subscription and manually created orders from being touched at all.

Anything you have not allowed simply does not appear on the Order Status page. The customer is not shown a control that will reject them; they are shown the changes they can actually make, and a link to your support channel for anything else.