[{"data":1,"prerenderedAt":48},["ShallowReactive",2],{"article-en-ai-needs-customer-insight-not-just-code":3},{"article":4,"related":17,"prevArticle":37,"nextArticle":41,"availableLocales":45},{"id":5,"slug":5,"title":6,"excerpt":7,"content":8,"image":9,"date":10,"published":11,"status":12,"category":13,"keywords":14,"meta_description":15,"og_image":16,"custom_css":16,"created_at":10,"updated_at":10},"ai-needs-customer-insight-not-just-code","Two things we learned from a North American e-commerce project","Building a decision platform last year for cross-ocean replenishment and fulfilment risk across two North American warehouses, we confirmed again that the hard part is not plugging AI into a system. It is understanding the timing, constraints and consequences of every decision.","\u003Cp>Last year, we built a decision platform for cross-ocean replenishment and fulfilment risk across two North American warehouses.\u003C/p>\n\n\u003Cp>On the surface, it is a supply chain system: suppliers in China, two warehouses in LA and Houston, multi-channel sales, retailer POs, ocean booking, customs clearance, freight rates, cross-region fulfilment and transfers.\u003C/p>\n\n\u003Cp>But once we started taking it apart, we found it wasn't really a \"forecasting\" problem, and it wasn't \"a dashboard with AI\" either. What it deals with is this: when information is incomplete, risks keep shifting and every action affects the next one, what should we decide today?\u003C/p>\n\n\u003Cp>The experience made us more certain of one thing: using AI to write a system is no longer the hardest part. The hard part is whether the team can take in the scenarios, constraints and consequences in an industry that nobody has spelled out yet.\u003C/p>\n\n\u003Cp>I want to write down the two things from this project that struck us most.\u003C/p>\n\n\u003Ch2>First: the model can't live after the fact, it has to live in the moment\u003C/h2>\n\n\u003Cp>Many numbers in a supply chain look intuitive.\u003C/p>\n\n\u003Cp>When the goods will arrive.  \nHow much stock is left.  \nWhat the quote is.  \nWhether a shipment was inspected.\u003C/p>\n\n\u003Cp>But when you actually make a decision, what matters most is often not the final answer but: \u003Cstrong>on that day, at that moment, what could we actually see?\u003C/strong>\u003C/p>\n\n\u003Cp>For example, a later-updated ETA can't be treated as information that was known at the time. The final invoice can't be used to pretend we knew the cost from the start. Inspection results can't show up early in a backtest. These look like small data engineering details, but they directly decide whether the model is fooling itself.\u003C/p>\n\n\u003Cp>If a model uses information that only became known later, of course it looks accurate.  \nBut that isn't predictive power. It is just hindsight.\u003C/p>\n\n\u003Cp>So in this system we paid close attention to when events happened, when data first became visible, rule versions, and the state snapshot at every decision timestamp. Not because these things are technical, but because the real world doesn't let you go back and make decisions with the answers in hand.\u003C/p>\n\n\u003Cp>We see this as a turning point where AI starts to have real value: not just computing data faster, but being able to state the uncertainty clearly when the information available right now is incomplete.\u003C/p>\n\n\u003Cp>Not just an ETA, but an arrival window and its risk.  \nNot just whether to transfer stock, but what could happen under each scenario and how likely it is.  \nNot just which option is cheapest, but stockouts, service commitments, customer relationships and downstream opportunity costs laid out side by side.\u003C/p>\n\n\u003Cp>This isn't only a model capability. Behind it you need an understanding of the problem itself.\u003C/p>\n\n\u003Ch2>Second: people are not a sign-off before AI goes live, they are part of how the system learns\u003C/h2>\n\n\u003Cp>A typical question in this project: should Houston's stock be used to save orders on the West Coast?\u003C/p>\n\n\u003Cp>Looking at a single order, the answer might be simple. The West Coast is out of stock, Houston has stock, so ship across regions.\u003C/p>\n\n\u003Cp>But look one layer further and things change.\u003C/p>\n\n\u003Cp>Sending this stock to the West Coast might save a high-margin order, but it might also leave Houston's own region short at the next demand peak. In between there are cross-region shipping costs, promised dates, retailer penalties, warehouse capacity and long-term customer value.\u003C/p>\n\n\u003Cp>A mature system shouldn't just output the two words \"recommend transfer\".\u003C/p>\n\n\u003Cp>At the very least it has to make clear:\u003C/p>\n\n\u003Cul>\n\u003Cli>Under what scenario this action is worth taking.\u003C/li>\n\u003Cli>What you lose by not doing it, and what risks doing it carries to the next stop.\u003C/li>\n\u003Cli>Whether it hits a hard constraint that no cost saving can offset.\u003C/li>\n\u003Cli>If a person decides to change the recommendation, what they changed and why.\u003C/li>\n\u003C/ul>\n\n\u003Cp>That is how we understand human-in-the-loop.\u003C/p>\n\n\u003Cp>People are not there to click \"approve\" before the model goes live. Human approvals, changes, rejections and deferrals are all important signals in themselves. They may reflect customer relationships, compliance conditions, conditions on the ground, or business judgement that hasn't been written into the rules yet.\u003C/p>\n\n\u003Cp>But human judgement can't just stay in chat logs either.\u003C/p>\n\n\u003Cp>Which candidate options the model proposed at the time, what the person finally chose, what was actually executed, and what really happened weeks or months later all have to be kept. Only then can the system build a decision loop that can be replayed, instead of guessing from scratch every time.\u003C/p>\n\n\u003Cp>We are increasingly sure that if AI is going to work in complex operations, what it has to learn is not \"did a person click approve\", but why the person made that choice in that scenario, and what that choice led to in the end.\u003C/p>\n\n\u003Ch2>In complex scenarios, the hard part was never wiring up the model\u003C/h2>\n\n\u003Cp>Many things can be turned into a demo very quickly now.\u003C/p>\n\n\u003Cp>Pulling data, connecting a model, building an interface and having it generate recommendations: the bar for all of this really is coming down. That is a good thing.\u003C/p>\n\n\u003Cp>But once you actually get into an industry, the difficulty doesn't disappear. It just shifts from \"can it be done\" to \"do we know how it should be done\".\u003C/p>\n\n\u003Cp>Which data only became known afterwards and can't be used for training.  \nWhich rules are hard constraints that the model can't trade away for higher revenue.  \nWhich averages hide failures for key customers, specific routes or specific warehouses.  \nWhich actions look like they save one region but really just move the risk somewhere else.\u003C/p>\n\n\u003Cp>None of these questions can be answered by a model name alone.\u003C/p>\n\n\u003Cp>It takes customer insight, and it takes problem insight. Put more directly, it needs a team willing to walk into the details with the business, and bit by bit pull out, define and record the judgements that were scattered across the experience of different roles.\u003C/p>\n\n\u003Cp>This is a lot of what we have been doing this year.\u003C/p>\n\n\u003Cp>We don't start with an AI solution and then look for problems to fit it to. We first get a clear view of where each industry is really stuck, then decide how models, rules, data and people should be combined.\u003C/p>\n\n\u003Cp>Some situations suit automation.  \nSome should only produce recommendations.  \nIn some, the most important thing is for the system to know: there isn't enough data right now, stop and hand it to a person.\u003C/p>\n\n\u003Ch2>When decisions start drawing on more than a hundred data sources at once\u003C/h2>\n\n\u003Cp>In the end the project connected \u003Cstrong>over a hundred data sources, several thousand fields and more than a thousand key factors\u003C/strong>. Demand, inventory, retailer POs, ocean booking, cross-ocean milestones, customs clearance, freight rates, external weather signals, and what was actually executed after human review all had to line up by SKU, warehouse, channel and time.\u003C/p>\n\n\u003Cp>It sounds like data integration, but the difficulty was never just getting the data in. Every piece of information changes the judgement on the next action: replenish first, change the warehouse allocation, ship direct across regions, or do nothing. The system has to put inventory turnover, stockout risk, service commitments, logistics cost and contribution margin on the same decision ledger in real time, so the team doesn't need a chain of manual relays and spreadsheet calculations to know how a given shipment should move.\u003C/p>\n\n\u003Cp>As a result, both inventory turnover and gross margin improved significantly. The project paid back in under a year, and at the time of writing the ROI is over 300%.\u003C/p>\n\n\u003Cp>But this result was never ours alone. It came from an owner willing to invest for long-term value, and from an internal team that gave its full cooperation so that data, processes and on-the-ground judgement could be laid out and worked on together. Rarer still, when the small mistakes that are inevitable early in a rollout appeared, the team chose to fix and recalibrate together instead of giving up the first time things weren't perfect. These conditions, which seem to sit outside the system, are what let the project end with such strong results.\u003C/p>\n\n\u003Ch2>Closing\u003C/h2>\n\n\u003Cp>Looking back at this two-warehouse supply chain project, what we delivered was more than a design baseline for models and rules.\u003C/p>\n\n\u003Cp>More importantly, we confirmed again something we have always believed: AI's maturity is not about how clever it looks, but whether it understands what kind of uncertainty it is facing, whether it can state constraints and consequences clearly, and whether it can work with human experience to make complex decisions more steadily.\u003C/p>\n\n\u003Cp>What really creates value in an industry is not just putting AI into a system.  \nIt is putting in the scenarios and judgements the system never saw before, too.\u003C/p>","https://cdn.sqa.tw/articles/ai-decision-complexity-supply-chain-2026-08-17.png","2026-08-17T02:30:00+00:00",true,"published","industry","AI decision systems, supply chain AI, situational insight, scenario insight, human-in-the-loop, point-in-time data","Lessons from a two-warehouse North American replenishment platform on scenario insight, point-in-time data discipline and human-in-the-loop decision loops.",null,[18,25,31],{"id":19,"slug":19,"title":20,"excerpt":21,"image":22,"date":23,"category":24},"ai-development-sdlc-release-verification","When AI builds it in two hours but verification still takes three days","Once AI speeds up development, spec sign-off, testing and release do not automatically speed up with it. Using a real case from a booking system SaaS, we describe how we adjusted the SDLC to cut full release verification from two or three days to under two hours, and how the SQA role changed along the way.","https://cdn.sqa.tw/articles/ai-sdlc-verification-bottleneck-cover.jpg","2026-11-05T12:00:00+08:00","perspective",{"id":26,"slug":26,"title":27,"excerpt":28,"image":29,"date":30,"category":24},"sme-guide-to-choosing-ai-agent","AI agents are everywhere. How should a small business choose one?","We were recently asked to run a full post-deployment review of an AI agent, and found it had quietly caused five times too much raw material to be ordered from customer order emails, and nearly created a liquidity risk on the finance side. The problem with agents is rarely that they are not smart enough. It is that nobody asked the right questions.","https://cdn.sqa.tw/articles/sme-agent-black-box-inspection.jpg","2026-09-01T15:00:00+00:00",{"id":32,"slug":32,"title":33,"excerpt":34,"image":35,"date":36,"category":24},"ai-coding-team-collaboration-three-patterns","Three patterns we see once AI coding reaches the team","After working with more than ten development teams over the past six months, we keep seeing the same thing: individuals getting faster with AI does not mean the team is ready to get faster together.","/images/blog/ai-coding-teams-editorial.jpg","2026-08-20T08:00:00+00:00",{"slug":38,"title":39,"date":40},"qaptly-v0175-codex-support","Qaptly Desktop now supports Codex","2026-05-16T13:01:00+00:00",{"slug":42,"title":43,"date":44},"why-we-are-reintroducing-dbam-ai","Why we rebuilt SQA.TW","2026-08-17T16:00:00+00:00",[46,47],"en","zh",1794970112850]