A brochure site that nobody maintains decays slowly. A store that nobody maintains breaks on a schedule — because a store isn’t just your website, it’s your website plus a half-dozen outside services that keep moving whether you do or not.

The moving parts a store depends on

Payment processors retire API versions on published timelines. Stripe, PayPal, Authorize.net — all of them periodically end support for old integration methods, and a checkout built on a retired one stops taking money on the retirement date, not gradually.

Tax rules change every year. Rates shift, nexus rules shift, and since the Wayfair decision put most online sellers on the hook for other states’ sales tax, “we’ll just charge our home rate” hasn’t been a safe answer.

Shipping carriers reprice constantly and revise their APIs on their own clock. A store quoting last year’s rates is quietly paying the difference on every order.

PCI compliance is an annual obligation with real teeth, not a one-time checkbox — more on that in the plain-language version.

None of these care whether your developer is still around. They move, and an unmaintained store falls behind relative to them — like a dock line that isn’t tended while the water level changes.

What that means for upkeep

Commerce maintenance runs on the same five jobs as any maintenance plan, plus two habits specific to money: a monthly test transaction (a real card, a real order, then a refund — the only true test of a checkout) and someone reading the processor’s emails, because that’s where API retirements are announced, usually months ahead, usually to an inbox nobody checks.

The stakes are just plainer here. A brochure site down for a week is embarrassing; a checkout silently failing for a week is revenue you don’t get back. If your store’s maintainer has already drifted away, what breaks first is the natural next read.