<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Buyer Experience on O2O Sourcing | China, Seen from the Ground</title>
    <link>https://o2osourcing.pages.dev/tags/buyer-experience/</link>
    <description>Recent content in Buyer Experience on O2O Sourcing | China, Seen from the Ground</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 24 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://o2osourcing.pages.dev/tags/buyer-experience/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Write a Useful Sourcing Diary From One Concrete Order Problem</title>
      <link>https://o2osourcing.pages.dev/blog/how-to-write-a-useful-sourcing-diary-from-one-concrete-order-problem-ingva1/</link>
      <pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://o2osourcing.pages.dev/blog/how-to-write-a-useful-sourcing-diary-from-one-concrete-order-problem-ingva1/</guid>
      <description>&lt;h2 id=&#34;executive-introduction&#34;&gt;Executive introduction&lt;/h2&gt;&#xA;&lt;p&gt;A sourcing diary is not a complaint log or a polished success story. It records what the buyer expected, what the documents specified, what happened, what evidence exists, which questions remain open, and what must change before the next purchase order.&lt;/p&gt;&#xA;&lt;p&gt;The most useful diary follows decisions rather than merely recounting events. A chronological narrative may explain that samples were approved, production finished, payment was authorized, and defects appeared after delivery. A decision-based record goes further: it shows which assumptions were left unwritten, which revision controlled production, what evidence was available at each payment milestone, and why a risk remained open.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
