<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/feed.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Commerce at Scale — Studies</title>
    <link>https://commerceatscale.com/studies</link>
    <description>Design studies in commerce at scale: one problem each, the options, and the reasoning behind the choice.</description>
    <language>en-GB</language>
    <lastBuildDate>Wed, 12 Aug 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://commerceatscale.com/feed.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>What a good specification settles</title>
      <link>https://commerceatscale.com/studies/specification-settles</link>
      <guid isPermaLink="true">https://commerceatscale.com/studies/specification-settles</guid>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <description>A specification's job is to close the decisions the build would otherwise have to guess at. The ones worth settling are rarely on the happy path — they are the edges, and settling them early keeps each choice with the people whose choice it is.</description>
    </item>
    <item>
      <title>Using AI as a consistency engine for architecture work</title>
      <link>https://commerceatscale.com/studies/ai-consistency-engine</link>
      <guid isPermaLink="true">https://commerceatscale.com/studies/ai-consistency-engine</guid>
      <pubDate>Wed, 29 Jul 2026 00:00:00 GMT</pubDate>
      <description>Most stories about AI in engineering are about writing code faster. The more useful question for an architect is whether it can make the thinking more consistent without taking over the decisions. Fix the structure, keep the judgement.</description>
    </item>
    <item>
      <title>Where the boundaries go in a multi-brand platform</title>
      <link>https://commerceatscale.com/studies/multi-brand-seams</link>
      <guid isPermaLink="true">https://commerceatscale.com/studies/multi-brand-seams</guid>
      <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
      <description>One platform serving many brands and markets depends on where you draw the boundaries. Put the boundary where ownership and speed of change differ. Shared, stable behaviour on one side. Brand and market differences on the other, written as configuration and not as copies.</description>
    </item>
    <item>
      <title>Handling order events after checkout, and the one thing that cannot wait</title>
      <link>https://commerceatscale.com/studies/order-event-bus</link>
      <guid isPermaLink="true">https://commerceatscale.com/studies/order-event-bus</guid>
      <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
      <description>Connecting every downstream system directly into checkout makes checkout fragile. Recording the order once and letting each system pick it up on its own time removes that risk — as long as you are honest about the one step that must still happen while the shopper waits.</description>
    </item>
    <item>
      <title>Setting up a large storefront estate without drift</title>
      <link>https://commerceatscale.com/studies/provisioning-without-drift</link>
      <guid isPermaLink="true">https://commerceatscale.com/studies/provisioning-without-drift</guid>
      <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
      <description>When sites are set up by hand, no two end up the same. Making the configuration the single source of truth — and making the step that applies it safe to repeat — turns setup from weeks into days and stops the differences at the source.</description>
    </item>
  </channel>
</rss>
