Maintain a carriers JSON array column per platform. Vendors publish supported carrier lists on their integration pages; refresh quarterly or when a major carrier integration launches. The per-platform page and every pair page render the same carrier grid from the same column, so a new FedEx Ground integration shows up everywhere on the next cache cycle.

Add a usps_discount column with the platform's discount tier (Commercial Plus, Commercial Base, or N/A). Conditional rendering through selector mapping shows a discount badge only when applicable. Pirate Ship's no-subscription Commercial Plus claim and ShipStation's tiered discounts both render correctly from the same column logic.

Use a pricing_model column (subscription, per-label, hybrid) and separate columns for monthly_fee and per_label_fee. Conditional rendering displays both numbers for hybrid platforms like EasyPost, monthly only for ShipStation, and per-label only for Pirate Ship. The same logic drives both per-platform and pair page pricing displays.

Yes. Run two page groups with different templates scoped by order_volume_fit, one emphasizing SMB hands-off setup and the other emphasizing enterprise rate negotiation and custom carrier integration. Both read from the same master sheet with filters, keeping updates centralized while letting the page match the buyer's evaluation criteria.

Add an affiliate_url column to the platforms sheet and map it through selector mapping into the CTA button. When a shipping vendor migrates its partner program URL format, edit one cell and every page that references the platform updates the link automatically on the next cache flush across both per-platform and pair pages.

Yes. The pairs sheet has a verdict column written per pair, distinct from the per-platform verdicts. Selector mapping injects the pair-specific verdict alongside the joined platform data. This keeps ShipStation-vs-Shippo pages substantive rather than templated, which is what ranks for ecommerce shipping evaluation queries.

Drop the row. The URL stops generating on the next cache cycle and falls out of the sitemap. Pair pages that referenced the dropped slug also stop generating because the join fails. Set up a 301 redirect on the retired slug to the closest current platform to preserve any backlinks that were pointing at the old comparison.

Add a regions column (US, UK, AU, CA) and use selector mapping with conditional rendering keyed on locale. Generate region-specific page groups at /shipping-software/uk/{slug}/ if your audience splits regionally. The same master sheet drives all regions through different column selections per page group, keeping updates centralized.