Placing an order, and what it tells the person receiving it

You choose a listing and confirm it. A record appears on the vendor's side of the platform saying that somebody has committed to a purchase.

Placing an order is a small act with two audiences. The person selling sees it because they have to fulfil it. The platform sees it because the platform created it. Nothing else in the catalogue sees the order as an order, though several observers see consequences of it later.

It is worth separating the order from everything around it. Browsing is a different action with a different observer profile, covered in browsing listings while signed in. Supplying a place is a different action again, covered in the address you hand over. This card is only about the moment of commitment.

What the vendor learns

The order arrives attached to an account name. From that alone the vendor gets a short, precise set of facts.

• That a specific account, identified by its handle, placed the order.
• Which listing was chosen out of everything they offer.
• The quantity or option selected, whichever the listing exposes.
• The timestamp, to whatever precision the platform shows.
• The shipping option chosen, where the listing offers more than one.
• The order state, so they can see it was funded, held or cancelled.

Two of those are more informative than they look. The shipping option can imply a region, because options are often organised by where a parcel is going, and choosing one narrows you before you have typed a single letter of an address. The timestamp accumulates: a single order says nothing about your habits, and the third order at the same hour of the evening starts to describe a routine.

The account handle is the spine of everything. It is the key that lets the vendor connect this order to any message you sent before it and any order you place after it. That is the subject of ordering twice.

What the vendor does not learn

The gap here is wide, and readers get it wrong in both directions.

• Your name. Nothing in the ordering step carries one.
• Your IP address, your country by connection, or anything about your network. The vendor has no view of the wire at all.
• Where you are, at this point in the process. Until an address is supplied the vendor has a region hint at best.
• Whether this is your first order anywhere, or your five hundredth. They can see your history with them. They cannot see your history with anyone else.
• What device you used, what browser, what operating system, whether you were on a phone.
• Whether the account is one person, several people, or somebody using it once on behalf of another.
• Anything about how you paid beyond the fact that the platform says the order is funded.

That last one surprises people. The vendor is generally looking at a platform state, not at a payment trail, and the movement of funds is a separate question with a separate observer set. Funding a market balance covers that side.

One more absence matters. An account with no order history looks like a new account. It does not look like a new person. The two are not the same thing, and no vendor can distinguish them from the order screen.

One action, two records

The order exists twice at once. The vendor sees a job to do. The platform sees a row in its own ledger, and the platform's copy is the one that persists independently of both parties.

The right hand column is why this branch keeps pointing back to the market server. The vendor sees one relationship. The platform sees every relationship at once, and that is a structurally different kind of knowledge.

What the order looks like a week later

Orders do not stay fresh. On the platform the row remains and carries a status. On the vendor side the order may have been copied into whatever they use to keep track of work in progress, and that copy has no expiry that you can see or influence.

This is the point where the human nature of this observer starts to matter. A server would age the record out on a schedule. A person keeps it as long as it is useful and sometimes long after, for reasons that are entirely mundane.

What changes the answer

5 things change how much this action gives away. None of them takes it to zero, and none of them is a promise.

1. Keep the order and the conversation separateAn order carries a fixed set of fields. A message carries whatever you decide to write. Most of what a vendor ends up knowing about a buyer arrived through the second channel, not the first. Asking a question first looks at what that channel gives away.
2. Notice what the shipping option impliesChoosing a regional option discloses a region before any address is typed. This does not stop being true if you later supply an address elsewhere, because both choices are visible to the same observer. It is a narrowing, not an identification.
3. Remember the timestamp accumulatesOne order has a time. Several orders have a pattern. Nothing about a single purchase reveals a routine, and nothing about a routine can be unlearned by the observer once it is visible.
4. A fresh account resets history, not behaviourA new handle removes the visible order history, as covered in registering an account. It does not change an address, a writing style or a habit of ordering at the same hour, and those are what link accounts to each other in practice.
5. The platform sees more than the vendor hereIf your concern is the breadth of what one party can see, the order step is a server problem more than a vendor problem. The vendor sees their own corner. The server sees the whole floor.

What this card is not

This card is not advice about what to buy, from whom, or whether to order at all. It describes what the act of ordering discloses and to which observer.

Questions that come up

Does a vendor know if I cancelled an order with somebody else?

No. A vendor sees the orders placed with them. Order history across the rest of the platform is visible to the platform, not to individual sellers.

Is the order visible to my ISP?

No. Your network observer sees an encrypted connection of a certain shape and duration, described in the shape of the traffic. It does not see what was on the page.