<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>BrewOS Blog</title><link>https://brewos.dev/blog/</link><description>Field notes on enterprise route-to-market software.</description><item><title>When a dropped photo costs a rep their bonus</title><link>https://brewos.dev/blog/gospotcheck-photo-loss-rep-pay</link><guid>https://brewos.dev/blog/gospotcheck-photo-loss-rep-pay</guid><pubDate>Sun, 28 Jun 2026 09:00:00 GMT</pubDate><description>When a retail-execution app drops a rep&#x27;s photo or clears their answers, the lost sync becomes a payroll dispute. Why persistence bugs hit incentive pay.</description></item><item><title>Deploy to find your syntax errors: debugging SAP CPI</title><link>https://brewos.dev/blog/sap-cpi-groovy-debugging-message-pricing</link><guid>https://brewos.dev/blog/sap-cpi-groovy-debugging-message-pricing</guid><pubDate>Fri, 26 Jun 2026 09:00:00 GMT</pubDate><description>Debugging SAP CPI means deploying to find Groovy syntax errors, racing a 10-minute trace window, and watching per-message pricing inflate the bill.</description></item><item><title>Earned today, visible tomorrow: loyalty&#x27;s batch accrual lag</title><link>https://brewos.dev/blog/loyalty-batch-accrual-lag</link><guid>https://brewos.dev/blog/loyalty-batch-accrual-lag</guid><pubDate>Tue, 23 Jun 2026 09:00:00 GMT</pubDate><description>Packaged loyalty platforms accrue engagement points in batch once a day, so members wait up to 24 hours. Why batch accrual lag quietly breaks loyalty mechanics.</description></item><item><title>Enterprise loyalty, enterprise rigidity: Epsilon reviews</title><link>https://brewos.dev/blog/epsilon-loyalty-flexibility-limits</link><guid>https://brewos.dev/blog/epsilon-loyalty-flexibility-limits</guid><pubDate>Wed, 17 Jun 2026 09:00:00 GMT</pubDate><description>Epsilon PeopleCloud Loyalty reviews flag campaigns you cannot edit after launch, speed limits and thin public data. What the flexibility limits mean for buyers.</description></item><item><title>The integration team everyone waits for</title><link>https://brewos.dev/blog/integration-team-bottleneck-centralized</link><guid>https://brewos.dev/blog/integration-team-bottleneck-centralized</guid><pubDate>Tue, 16 Jun 2026 09:00:00 GMT</pubDate><description>Why a centralized integration team becomes the bottleneck every cross-system feature waits behind, and what the shared middleware queue really costs.</description></item><item><title>The 29-day sandbox and other deployment stories</title><link>https://brewos.dev/blog/salesforce-deployment-change-sets-pain</link><guid>https://brewos.dev/blog/salesforce-deployment-change-sets-pain</guid><pubDate>Fri, 12 Jun 2026 09:00:00 GMT</pubDate><description>Why Salesforce deployment is hard: change sets can&#x27;t roll back, config records won&#x27;t travel, full sandboxes refresh every 29 days, and three releases a year.</description></item><item><title>Case note: credit checks that stopped blocking order capture</title><link>https://brewos.dev/blog/case-note-credit-limit-checks-realtime</link><guid>https://brewos.dev/blog/case-note-credit-limit-checks-realtime</guid><pubDate>Wed, 10 Jun 2026 09:00:00 GMT</pubDate><description>How we moved real-time credit limit checks off the synchronous ERP path: credit state as an event-driven projection, with a hard-block only at delivery.</description></item><item><title>The rule builder nobody can read six months later</title><link>https://brewos.dev/blog/talon-one-rule-builder-complexity</link><guid>https://brewos.dev/blog/talon-one-rule-builder-complexity</guid><pubDate>Fri, 05 Jun 2026 09:00:00 GMT</pubDate><description>Why the Talon.One rule builder is unreadable six months on: reviewers report missing descriptions, a freezing UI, 4-hour support caps and usage pricing.</description></item><item><title>Perfect store programs die in the last mile of data</title><link>https://brewos.dev/blog/perfect-store-photo-recognition-reality</link><guid>https://brewos.dev/blog/perfect-store-photo-recognition-reality</guid><pubDate>Wed, 03 Jun 2026 09:00:00 GMT</pubDate><description>Perfect store photo recognition works; the pipeline behind it doesn&#x27;t. Why shelf-scan data lands days too late to fix the store, and where the real fix lives.</description></item><item><title>&#x27;Works offline&#x27; until it doesn&#x27;t: the field-data reality</title><link>https://brewos.dev/blog/repsly-offline-sync-30-minutes</link><guid>https://brewos.dev/blog/repsly-offline-sync-30-minutes</guid><pubDate>Sat, 30 May 2026 09:00:00 GMT</pubDate><description>Field apps that claim to work offline hang or take 30 minutes to open. Why offline-first field data collection is an architecture, not a checkbox.</description></item><item><title>Does IBM Sterling OMS need its own ops team?</title><link>https://brewos.dev/blog/ibm-sterling-oms-heavyweight</link><guid>https://brewos.dev/blog/ibm-sterling-oms-heavyweight</guid><pubDate>Tue, 26 May 2026 09:00:00 GMT</pubDate><description>IBM Sterling OMS is the DOM flagship, but its heavy install, multi-JVM footprint and escalation-tier support mean order orchestration needs its own ops team.</description></item><item><title>Case note: a loyalty mechanic in five days, not five months</title><link>https://brewos.dev/blog/case-note-loyalty-mechanic-five-days</link><guid>https://brewos.dev/blog/case-note-loyalty-mechanic-five-days</guid><pubDate>Mon, 25 May 2026 09:00:00 GMT</pubDate><description>How we shipped a returnables-aware loyalty mechanic in five days, not the months an enterprise loyalty build takes: rules as config on one shared event bus.</description></item><item><title>SPDD, SPAU and the 35-minute transport</title><link>https://brewos.dev/blog/sap-s4hana-transport-upgrade-pain</link><guid>https://brewos.dev/blog/sap-s4hana-transport-upgrade-pain</guid><pubDate>Thu, 21 May 2026 09:00:00 GMT</pubDate><description>Why SAP S/4HANA upgrades slow commerce teams: SPDD and SPAU modification adjustment on every upgrade, plus community-reported 35-minute transports to Quality.</description></item><item><title>If the app needs 4G, the fragmented trade doesn&#x27;t have it</title><link>https://brewos.dev/blog/offline-first-ordering-fragmented-trade</link><guid>https://brewos.dev/blog/offline-first-ordering-fragmented-trade</guid><pubDate>Sun, 17 May 2026 09:00:00 GMT</pubDate><description>Offline-first order capture keeps B2B ordering working where the fragmented trade has no reliable 4G. Why enterprise storefronts fail offline, how to fix it.</description></item><item><title>Use it or lose it: CrowdTwist services hours that expire</title><link>https://brewos.dev/blog/oracle-crowdtwist-professional-services</link><guid>https://brewos.dev/blog/oracle-crowdtwist-professional-services</guid><pubDate>Wed, 13 May 2026 09:00:00 GMT</pubDate><description>Oracle CrowdTwist professional services hours expire in six to twelve months and forfeit unused, per Oracle&#x27;s own terms. Read the clause before signing.</description></item><item><title>MCP and the end of the integration project</title><link>https://brewos.dev/blog/mcp-api-first-enterprise-data</link><guid>https://brewos.dev/blog/mcp-api-first-enterprise-data</guid><pubDate>Tue, 12 May 2026 09:00:00 GMT</pubDate><description>An MCP server over a public API on live domain events ends the integration project: analytics, RGM models and AI agents plug in with a key, not a pipeline.</description></item><item><title>Case note: the console that retired the printed call sheet</title><link>https://brewos.dev/blog/case-note-telesales-console-replacing-call-sheets</link><guid>https://brewos.dev/blog/case-note-telesales-console-replacing-call-sheets</guid><pubDate>Fri, 08 May 2026 09:00:00 GMT</pubDate><description>How a telesales console replaced printed call sheets: one live customer timeline, a per-outlet suggested order, and why the commission model had to change.</description></item><item><title>7,000 tasks a day: how Workato recipe pricing compounds</title><link>https://brewos.dev/blog/workato-recipe-task-pricing</link><guid>https://brewos.dev/blog/workato-recipe-task-pricing</guid><pubDate>Tue, 05 May 2026 09:00:00 GMT</pubDate><description>Workato bills per task, not per order: a 7-action recipe run 1,000x a day is 7,000 tasks. How recipe-tier pricing, overages and connector surcharges compound.</description></item><item><title>Empty shelves, full warehouses: master data as destiny</title><link>https://brewos.dev/blog/haribo-target-canada-master-data</link><guid>https://brewos.dev/blog/haribo-target-canada-master-data</guid><pubDate>Thu, 30 Apr 2026 09:00:00 GMT</pubDate><description>Garbage master data produces full warehouses and empty shelves at once. Target Canada and Haribo&#x27;s SAP go-live show what bad master data does to a supply chain.</description></item><item><title>Why Antavo scores 59 out of 100 on implementation</title><link>https://brewos.dev/blog/antavo-implementation-scores-learning-curve</link><guid>https://brewos.dev/blog/antavo-implementation-scores-learning-curve</guid><pubDate>Mon, 27 Apr 2026 09:00:00 GMT</pubDate><description>Antavo scores 59/100 on ease of implementation and 54 on customization, below the loyalty category average. What the numbers mean for B2B beer loyalty.</description></item></channel></rss>
