> ## Content Index
> Fetch the complete content index at: https://abundance.alloconomy.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Now eComm Inc Is the Seller
- URL: https://abundance.alloconomy.com/alloconomy/commerce-the-platform-becomes-the-seller/
- Published: 2026-10-19T07:33:02.000Z
- Updated: 2026-10-22T22:21:05.000Z
- Description: Business purchasing, cloud billing and marketplace collection.
- Author: Sathya Narayanan
- Tags: Alloconomy, Supply Chain, Commerce, Behind the Buy Button, #series-detail, #Import 2026-10-18 23:22

Supply Chain · Sixteen essays

Behind the Buy Button

Complete reading path · You are in Part 12 of 16
1. Part 1 [I Bought a Book. What Had to Be Promised First?](https://abundance.alloconomy.com/alloconomy/behind-the-buy-button/) The cast, the cheat sheet, and the whole commercial system.
2. Part 2 [Maya Sells to eComm Inc. Maya Also Sells Through eComm Inc.](https://abundance.alloconomy.com/alloconomy/commerce-who-is-selling-to-whom/) Retail vendors, marketplace sellers, custody and direct fulfillment.
3. Part 3 [The Purchase Order Begins Before the Purchase Order](https://abundance.alloconomy.com/alloconomy/commerce-before-the-purchase-order/) Need, supplier identity, sourcing, approval and changing commitments.
4. Part 4 [Sent, Received, Accepted: Three Different Claims](https://abundance.alloconomy.com/alloconomy/commerce-sent-received-accepted/) Order lines, shipment assertions, receipt evidence and message status.
5. Part 5 [The $140 Disagreement Inside One Invoice](https://abundance.alloconomy.com/alloconomy/commerce-the-140-dollar-disagreement/) Two-, three- and four-way matching, disputes and settlement.
6. Part 6 [The Price After the Price](https://abundance.alloconomy.com/alloconomy/commerce-the-price-after-the-price/) Rebates, credits, working capital and realized supplier economics.
7. Part 7 [How Do You Receive an Hour of Work?](https://abundance.alloconomy.com/alloconomy/commerce-how-do-you-receive-an-hour/) Labor, maintenance and professional services need their own evidence.
8. Part 8 [Software Is a Promise Over Time](https://abundance.alloconomy.com/alloconomy/commerce-software-is-a-promise-over-time/) Access, usage, licenses, digital rights and renewal decisions.
9. Part 9 [A Printing Machine Is Not Yet Printing Capacity](https://abundance.alloconomy.com/alloconomy/commerce-a-machine-is-not-yet-capacity/) Manufacturing plans, advances, assets and readiness for use.
10. Part 10 [When the Project Changes, What Exactly Changed?](https://abundance.alloconomy.com/alloconomy/commerce-when-the-project-changes/) Scope, RFIs, approved changes, progress claims and retention.
11. Part 11 [Buying Power, Renting Space, Committing Time](https://abundance.alloconomy.com/alloconomy/commerce-power-space-and-time/) Electricity, financial energy settlements and leases.
12. Part 12 **Now eComm Inc Is the Seller**Current essay Business purchasing, cloud billing and marketplace collection.
13. Part 13 [One Transaction, Several Accounting Clocks](https://abundance.alloconomy.com/alloconomy/commerce-one-transaction-several-clocks/) Commitments, accruals, cash, assets and financial-statement scale.
14. Part 14 [A System That Can Remember Why](https://abundance.alloconomy.com/alloconomy/commerce-a-system-that-remembers/) Linking documents, quantities, time, corrections and independent evidence.
15. Part 15 [Safety Before Speed: What a Green Tick Cannot Approve](https://abundance.alloconomy.com/alloconomy/commerce-safety-before-speed/) Payment authority, supplier changes, duplicates, incentives and AI limits.
16. Part 16 [Follow the Promises Back to My Book](https://abundance.alloconomy.com/alloconomy/commerce-follow-the-promises-home/) A worked capstone and the bridge to the inbound and outbound series.

**Illustrative examples. Public sources. Personal views.**

I am Sathya Narayanan, writing in a personal capacity as I learn in public. The views, interpretations and teaching models are my own; they do not represent my employer or any other organization and carry no employer approval or endorsement. No confidential, proprietary or nonpublic employer information is used. Factual background comes only from publicly available sources. Maya of Stories Inc, the book vendor; Mayan of Sapiens Inc, the printing-machine supplier; and eComm Inc, the ecommerce company, are fictional teaching characters and companies. I appear as the customer in imagined scenes, not as a report of my actual purchases. These scenes do not describe any real company or its internal systems. The cases are separate teaching examples, not one continuous ledger. Scenario amounts, rates, terms and policies are illustrative assumptions unless expressly identified as dated public facts. Actual contracts, regulations, operations and economics require case-by-case analysis.

**Visual guide: the steps and the records they create**

[Open the buying and selling graph and quick definitions →](https://abundance.alloconomy.com/alloconomy/behind-the-buy-button/#buyer-seller-construct-map) See the industry names for PO, sales order, ASN, receipt, invoice and payment, with the steps that create or update each record.

Companion maps: [Inbound receiving](https://abundance.alloconomy.com/alloconomy/before-the-shelf/#buyer-seller-construct-map) · [Customer fulfillment](https://abundance.alloconomy.com/alloconomy/from-click-to-doorstep/#customer-fulfillment-construct-map)

*Part 12 of 16 · Behind the Buy Button*

## Mayan becomes the customer

Mayan uses eComm Inc's cloud service to run their print-management service. They also buy office equipment through eComm Inc's business storefront. The company that purchases printing machines from Sapiens Inc. now supplies that business with cloud services and office equipment.

We have not reversed every contract. We have added separate relationships. Reciprocal trade does not by itself establish barter, linked prices or permission to offset invoices.

[![Part 12: b2b storefronts & cloud. $5,000 = $200 + $4,800 Fictional teaching model.](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/behind-the-buy-button/figures/part-12.png)](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/behind-the-buy-button/figures/part-12.png?ref=abundance.alloconomy.com)

Gross collection is different from net remittance. CUSTOMER PAYS — $5,000 — Gross collection by authorized party; ASSUMED FEE — $200 — Illustrative platform deduction; SAPIENS INC. RECEIVES — $4,800 — Later seller remittance. Invented fee, not an AWS quote. The applicable agreement defines the roles. Fictional example; see the nearby table and prose for an accessible explanation.  
[View the full-size diagram →](https://storage.ghost.io/c/f5/a9/f5a9f801-5a10-44d6-b07c-6658660be1a9/content/images/behind-the-buy-button/figures/part-12.png?ref=abundance.alloconomy.com)

## The seller-side cheat sheet

| Case                 | What Mayan is buying                      | What the platform role might be                                  |
| -------------------- | ----------------------------------------- | ---------------------------------------------------------------- |
| Business storefront  | Physical goods from the identified seller | Storefront, integration, selling or service role as specified    |
| Cloud services       | Contracted usage or access                | Provider of its own services                                     |
| Software marketplace | A third party's offering                  | Marketplace, billing or collection role under the relevant terms |

A familiar checkout does not make these identical. [AWS Marketplace's agreement structure](https://docs.aws.amazon.com/marketplace/latest/userguide/contract-structure-seller.html?ref=abundance.alloconomy.com) distinguishes the underlying offering agreement from participants' agreements with AWS. The relevant terms, seller and billing entity must be checked for the particular transaction.

## The shopping cart returns to the buyer's approval process

Suppose a Sapiens Inc. employee selects ten monitors at $300 each. The $3,000 cart represents a proposed purchase. In our fictional process it returns to Sapiens Inc. for approval before the order is placed.

That illustrates a pattern called punchout: shopping happens in a supplier catalog while purchasing approval remains in the buyer's system. AWS's [procurement-integration documentation](https://docs.aws.amazon.com/marketplace/latest/buyerguide/procurement-system-integration.html?ref=abundance.alloconomy.com) describes such an approval flow. The software integration is a bridge between organizations, not a reason to forget the buyer's authority.

If six monitors arrive first, Mayan's receiver should record six, leaving four open. Amazon Business's [2023 three-way-match launch announcement](https://press.aboutamazon.com/2023/3/amazon-business-launches-3-way-match-for-mobile-app?ref=abundance.alloconomy.com) gives a public example of customer-side receiving and matching. It is evidence about a product for business customers, not Amazon's own internal accounts-payable procedure.

## A PO reference is not a cloud spending brake

Assume Mayan authorizes $10,000 of cloud usage for a period but their systems consume $12,000\. A PO number on the invoice does not erase the $2,000 difference.

[AWS Billing documentation](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/manage-purchaseorders.html?ref=abundance.alloconomy.com) describes selecting a PO for invoice association using criteria such as entity, period, charge type and balance. It does not establish a hard consumption stop. The Marketplace integration documentation separately says usage estimates do not cap actual charges.

Mayan therefore needs both purchasing authority and operational usage controls. The contract determines the actual obligation; a budget overrun is a question to investigate, not automatic proof that the provider cannot bill the service.

## A quantity of 1,200,000 may not mean a million products

The AWS integration documentation contains a revealing encoding rule. Certain usage or multiple-charge offers are represented as quantity-based Material lines priced at $0.01 per transport unit. The quantity preserves a monetary amount.

For an illustrative $12,000 arrangement, **$12,000 ÷ $0.01 = 1,200,000 transport units**. These are not necessarily licenses, users, print jobs or server-hours. The actual economic units come from the agreement and usage records.

This is why I would keep the original representation and its meaning together. A system can reconcile the invoice amount perfectly while producing an absurd “cost per license” because it misread the quantity field.

## Customer payment and supplier remittance are separate events

Now assume a business customer pays $5,000 for Mayan's software through eComm Inc's marketplace. Under the fictional collection terms, the platform is authorized to receive that payment for Mayan. It later remits $4,800 after an assumed $200 fee.

**Gross collection $5,000 = seller remittance $4,800 + assumed fee $200.**

The customer's payment was $5,000, not $4,800\. The platform fee is not Mayan's production cost. The timing of the customer's discharge and Mayan's bank receipt depends on the terms. [AWS's seller terms, Payments section](https://aws.amazon.com/legal/seller-terms/?ref=abundance.alloconomy.com) provide a scoped public example of authorized processing-agent collection and later remittance; our amounts are unrelated to its fees.

Mayan should reconcile the gross transaction, permitted deductions and cash received. eComm Inc should preserve each contractual role. An investor should distinguish money passing through a platform from revenue it earns. I, as a customer, should not have to pay a settled obligation again merely because the supplier's later remittance has not arrived; whether it is settled must be established from the actual authorized collection arrangement.

## Continue the series

Previous: [Buying Power, Renting Space, Committing Time](https://abundance.alloconomy.com/alloconomy/commerce-power-space-and-time/). Next: [One Transaction, Several Accounting Clocks](https://abundance.alloconomy.com/alloconomy/commerce-one-transaction-several-clocks/). Return to [the introduction and cheat sheet](https://abundance.alloconomy.com/alloconomy/behind-the-buy-button/).

*Evidence and method: public references were checked on October 18, 2026\. The fictional scenarios, proposed controls and design conclusions are learning models, not claims about a real employer. Reported financial figures retain their stated measurement dates.*