01Start here
Cornerstone
From million-row supplier catalogues to AP bills: how we turned Medusa into a property procurement platform
How WeAreSouk extended Medusa across supplier catalogues, property organisations, approvals, multi-vendor fulfilment, invoices and accounting.
Flagship case study
Multi-million-row imports
- 02How we kept a large supplier catalogue import from taking Medusa downHow a B2B marketplace turned large supplier files into an observable, recoverable Medusa import journey without tying catalogue work to one request.11 min
- 27The supplier import has been running for twenty minutes. Is it working, stuck or safe to resume?How we made long-running Medusa catalogue imports observable and recoverable with persisted phases, row-level state, resume and honest cancellation.10 min
AI procurement search
- 03When buyers describe a problem instead of a product: building AI procurement search on MedusaHow to turn ambiguous procurement language into a validated search plan while keeping catalogue, price, stock, access and geography rules in control.11 min
- 28“Find the cheapest dishwasher I can receive within two days.” How should Medusa search?How we combined lexical, hybrid and semantic retrieval without allowing AI to weaken Medusa price, stock, delivery, supplier or distance constraints.10 min
- 43“Find me the same thing, but cheaper.” How does the platform know what “the same thing” means?How we anchor AI product-equivalent discovery to a trusted SKU while preserving Medusa catalogue, stock, price and access rules.10 min
Approval and spend governance
- 04How we added purchase approvals without turning every Medusa order into a queueHow property-aware thresholds and progressive routing add financial control to Medusa while routine purchases keep moving through checkout.10 min
- 23The purchase was rejected. Why should the buyer have to start again?How we let buyers revise and resubmit a Medusa purchase while preserving approval history, recalculating routing and preventing competing decisions.10 min
- 33A £300 order can be riskier than a £3,000 order. Should approval depend on basket value alone?How we connected Medusa purchase approvals to property and GL budgets, external spend, marketplace spend and the current order—not basket value alone.10 min
Multi-vendor delivery, sites and geography
- 05The supplier has stock. But which site can actually fulfil the Medusa order?How a multi-vendor Medusa marketplace connects seller stock, physical sites, service zones and shipping choices through one fulfilment plan.10 min
- 24The supplier delivers to Houston, but not every address in Texas. How should Medusa decide?How we modelled seller delivery territories with country, state, city, postal and radius rules shared by catalogue discovery and Medusa checkout.10 min
- 25The product is in stock at three supplier sites. Which one should serve the property?How we connected property context, viable supplier stock, route-distance reuse and Elasticsearch to filter and rank Medusa products by nearest location.10 min
- 39The nearest store offers pickup. Why shouldn't every buyer see it?How we made store pickup a seller-owned, geographically eligible and stock-aware fulfilment path in a multi-vendor Medusa marketplace.10 min
Checkout, quotes and orders
- 06One buyer checkout, several sellers and sites: keeping the Medusa journey coherentHow a Medusa marketplace preserves one buyer journey while seller-specific shipping, approvals and fulfilment sites create several operational orders.10 min
- 16A purchase order is not a card payment: adding account terms to Medusa checkoutHow we added purchase-order terms to Medusa while separating checkout, validation, buyer confirmation and vendor capture.9 min
- 21The supplier changed the price. How do you turn that quote into a real Medusa order?How we kept seller negotiation, property context, delivery and GL allocations connected when an accepted quote became a Medusa order.11 min
- 34The buyer placed the order. Has the supplier actually accepted it?How we separated genuine vendor views, supplier acknowledgement or refusal and quantity-specific fulfilment in a Medusa marketplace.10 min
Vendor invoice validation
- 07The order says one thing. The goods receipt says another. Should Medusa release the invoice?How a Medusa procurement platform compares what was ordered, received and invoiced before a purchase-order payment can progress.10 min
- 26The supplier emailed three invoice PDFs. Which document should accounts payable trust?How we preserved every supplier invoice file, reviewed duplicates and replacements, and assembled one authoritative PDF around a Medusa purchase order.10 min
- 37The supplier invoice has no usable SKU. How do you match the line without letting AI guess?How we combine human invoice-line mapping with deterministic quantity, price and total checks in a Medusa procurement workflow.11 min
Accounting, allocations and RealPage
- 08When a Medusa purchase becomes a RealPage AP bill: keeping commerce and accounting in syncHow validated Medusa purchases become RealPage AP bills and how Posted, Partially Paid and Paid states return to an observable payment journey.10 min
- 17One order line, three properties: carrying GL allocations through MedusaHow we split purchased quantity across property units and GL accounts, preserved it through Medusa and derived balanced accounting values.9 min
- 29The Medusa order total is correct. Why can finance still not post it?How we translated reviewed Medusa orders into balanced GL-coded merchandise, shipping and tax rows while reconciling discounts and cents.10 min
- 45Finance needs cash by property. Which open orders should actually count?How we turned eligible unpaid Medusa orders into a role-aware funding report with property, GL-code and vendor visibility.11 min
Supplier organisation
- 09One supplier login for the whole team? We turned a Medusa seller into a real organisationHow a Medusa marketplace replaced shared supplier credentials with Admin, Store Manager and Account Manager roles scoped to real responsibilities.10 min
- 48A supplier can log in. Can they actually take an order?How we made Medusa supplier onboarding reflect current legal, store, delivery, payment and catalogue readiness instead of one completion flag.10 min
Property-management organisation
- 10One customer account, hundreds of sites: modelling a property business in MedusaHow we extended Medusa with organisations, properties, units and member perimeters so a multi-site buyer could purchase for the right place under the right authority.11 min
- 46Six people buy for fifty properties. Who can see, spend and approve what?How we combined six business roles with property scope so one Medusa organisation could support leadership, management, buying, wishlists and finance.11 min
- 56One company has 200 properties. Which one is actually buying?How we propagate one authorised property through Medusa catalogue, pricing, delivery and cart state without rewriting historical orders.10 min
Price lists, deltas, organisations and budgets
- 11A supplier price list should not rewrite your catalogue: how we imported it in MedusaHow we imported negotiated supplier prices into a controlled Medusa price list with streaming staging, scoped SKU matching, progress and cancellation.11 min
- 31A supplier sends a catalogue update. How do you change 8,000 products without rebuilding them?How we built a controlled Medusa catalogue-delta workflow that updates seller-owned products, preserves omitted fields and parks unknown SKUs for review.11 min
- 32Your suppliers already email spreadsheets. How do you turn them into controlled Medusa imports?How we turned supplier email attachments into authorised, mapped and traceable Medusa catalogue and inventory imports with durable sequencing.11 min
- 41A new client has properties, units and GL codes in three spreadsheets. How do they become ready to buy?How we turn property, unit and GL-account files into a tracked, organisation-scoped onboarding workflow in Medusa.11 min
- 42Finance sent a yearly budget workbook. How do you make it govern today's purchases without freezing the platform?How we validate, map and recover fiscal budget workbooks through a tracked background Medusa import.11 min
AI-assisted categorisation
- 12Too many products to classify by hand: building an AI categorisation pipeline on MedusaHow we grounded OpenAI Batch in a live Medusa taxonomy, streamed large artefacts and turned partial AI failures into a reviewable catalogue queue.12 min
- 50AI can categorise the product. How do you stop it inventing your catalogue?How we retrieve live Medusa category candidates with Elasticsearch, constrain AI choices and reject any category outside the product's stored set.10 min
- 51AI classified 3,000 products. Why doesn't the marketplace publish them?How a Medusa marketplace lets AI prepare supplier products while an administrator retains the final, tracked decision to publish them.10 min
Purchase-history intelligence
- 13“What did we buy last quarter?” Building Purchase History AI on MedusaHow we turned natural-language procurement questions into scoped, deterministic Medusa analytics without giving the model unrestricted database access.11 min
- 38One property paid far more for the same item. How do you find it before it becomes a pattern?How we surface unusual unit prices and replenishment cadence from governed, property-scoped Medusa purchase history.11 min
- 44Can an AI answer leak another property's spend without showing a single order?How we scope every conversational purchase-history row and aggregate to the authenticated user's accessible Medusa properties.10 min
Elasticsearch as a projection
- 14When search promises the wrong product: building a trustworthy Medusa marketplace indexHow we combined supplier, price, taxonomy, stock policy and delivery facts into one commercially useful Elasticsearch product projection for Medusa.11 min
- 47Your catalogue changed in Medusa. How do you stop search from telling yesterday's story?How we reconcile a Medusa catalogue with Elasticsearch using resumable batches, version comparison, locks, item-level retry and orphan repair.11 min
- 52Search shows the product. The product page says no. How do you stop a B2B catalogue contradicting itself?How we enforce one organisation-and-property catalogue policy across Elasticsearch discovery and Medusa REST hydration.10 min
Operational control centre
- 15Your marketplace does not need more alerts. It needs an operator Control CenterHow we turned approvals, imports and background failures across a Medusa marketplace into one deduplicated operational action queue.11 min
- 53The import still says “running”. Is it slow, stuck or already gone?How we track parent and child Medusa workflows, preserve durable operational history and distinguish stale activity from terminal failure.10 min
Assortment, compliance and credit
- 18The marketplace has 200 suppliers. Which ones should this organisation be allowed to buy from?How we combined delivery coverage, credential approval and procurement selection into an organisation-specific Medusa marketplace assortment.9 min
- 19One company, twenty properties, different credit decisions: modelling supplier terms in MedusaHow we modelled supplier account terms as a versioned, property-specific approval instead of a global purchase-order flag in Medusa.9 min
- 49Procurement approved the supplier. What happens when their compliance file changes?How private, versioned supplier documents, organisation review and procurement selection govern Medusa catalogue eligibility.10 min
Security, isolation and performance
- 20One Medusa backend, three applications: keeping buyers, sellers and operators in their own laneHow we separated Store, Vendor and Admin capabilities in a Medusa marketplace, then enforced seller, organisation, property and role scope on each resource.11 min
- 30The operations page shows 15 orders. Why should the API load the whole company?How we kept Medusa order, property, member and dashboard screens bounded with database filtering, counting, aggregation and page-level enrichment.11 min
- 40A supplier uploaded a CSV. What stops another seller—or another workflow—from using it?How owner-, purpose- and state-bound upload sessions secure direct file ingestion across a multi-sided Medusa marketplace.11 min
Claims, returns and documents
- 22The order was placed. Can everyone now produce the right procurement document?How we generated seller-scoped purchase orders and a connected procurement document trail from Medusa while preserving references and history.10 min
- 35The parcel was wrong. Should the platform rewrite what the buyer originally ordered?How we built a Medusa delivery-claim journey for missing, damaged or wrong goods while preserving order history and coordinating stock, tax and invoices.10 min
- 36The buyer returned two units. Which warehouse gets the stock—and which payment should change?How we connected Medusa returns to seller locations, physical receipt, purchase-order adjustments and provider-aware refunds in a multi-vendor marketplace.10 min
Two operational panels on one Medusa Cloud build
Inventory imports
- 55Your supplier sends a million stock rows. How do you update Medusa without freezing the marketplace?How we stream supplier stock into PostgreSQL staging, validate ownership in sets and update Medusa Inventory through bounded transactions.10 min
- 72Stock came back yesterday. Why is the product still missing from search?How durable stock-visibility state and reconciliation repair drift between Medusa inventory and Elasticsearch discovery.9 min
Free shipping and delivery promises
Asynchronous workflows at cloud scale
- 58The supplier import started. Then Medusa Cloud lost the workflow.Why a Medusa workflow can work locally but stall on a Cloud Scale worker, and how named resources, explicit roles and a durable diagnostic fix it.11 min
- 67Should the buyer wait, or should Medusa finish the job in the background?How to choose synchronous or asynchronous Medusa execution from the client's waiting, progress and recovery needs.10 min
- 68One catalogue import triggered six workflows. Which one actually stopped?How stable transaction IDs and parent-root ancestry turn nested Medusa workflows into one operator-readable business story.10 min
Account-manager territories
- 59Your sales rep owns the Northeast. Why can they still open a Texas order?How we turned supplier roles, geographic territories and customer portfolios into enforceable property-scoped access across a Medusa marketplace.11 min
- 69A new quote arrived. Which salesperson should see it?How a Medusa marketplace can route orders, quotes and commercial statistics through live Account Manager portfolios.9 min
Catalogue import operations
- 60The CSV uploaded perfectly. The products still could not be sold.How reusable supplier mappings and durable staging create complete draft Medusa products with pricing, inventory, fulfilment and review intact.10 min
- 61One supplier feed contained five different business decisions.How seller-scoped identity, normalized diffs and field-policy controls classify supplier rows before any Medusa catalogue mutation.10 min
- 65One unescaped comma moved the supplier’s price into the wrong column.How file preprocessing keeps CSV, TSV and Excel supplier exports aligned before Medusa catalogue mapping and staging.10 min
Product model and access security
- 62Buyers ask for the brand. Procurement reports on the manufacturer.How separate canonical Brand and Manufacturer identities keep supplier imports, search facets and order history trustworthy in Medusa.10 min
- 63No category was the honest answer. So we made ‘uncategorized’ useful.How constrained AI candidates, explicit refusal and fast manual review keep a changing Medusa product taxonomy trustworthy.10 min
- 66The supplier changed one image URL. Our product pages kept their media.How an asynchronous Medusa lifecycle turns remote supplier images into owned, optimized and operationally recoverable product assets.11 min
- 73A supplier pasted an image URL. Why should your Medusa backend trust it?How to secure Medusa supplier-image acquisition against SSRF, DNS rebinding, oversized decodes and content confusion.10 min
Notifications, messaging and support
- 64One order changed. The whole organisation did not need an email.How role, property, fulfilment location and account scope turn Medusa order events into targeted buyer and seller notifications.10 min
- 70The buyer wrote “Where is it?” Which order were they talking about?How to keep buyer-supplier messaging authorised and connected to properties, products and orders inside Medusa.10 min
- 71The dashboard says the email was opened. Did the customer actually read it?How to instrument Medusa email activity without turning a tracking-pixel fetch into proof of human attention.10 min
- 74A supplier needs every order in its own system. How do you open Medusa without losing control?How to connect Medusa marketplace orders to supplier systems with scoped configuration, signed payloads, tests and delivery evidence.10 min
Collaborative procurement
- 75One property, three buyers, four supply lists: how do you turn wishlists into procurement?How property-scoped lists, revisions and safe cart transfer turn a Medusa wishlist into a collaborative procurement workflow.9 min
- 76A buyer shared four products yesterday. Which price and stock should the colleague see today?How a Medusa comparison link preserves a shortlist while recalculating current price, stock, visibility and delivery context.9 min
- 79A buyer has 20,000 supplier SKUs in a CSV. How do you turn that file into a usable catalogue list?How to preserve supplier CSV rows, match SKUs within one seller catalogue and create a reviewable Medusa shopping list.9 min
Specialised AI agents
- 77An invoice arrived by email. How can AI read it without deciding who gets paid?How to extract supplier invoices asynchronously while deterministic Medusa rules and human review retain financial authority.9 min
- 78A catalogue gives buyers 40 technical fields. Which five facts actually help them purchase?How to generate stable procurement summaries from canonical Medusa product facts without embedding price, stock or invented claims.9 min
Related clusters