The FTC ordered nine companies on October 28 to supply information about how personal data influences prices and compensation. Walmart and Target are among them.

For ecommerce operators, the question worth asking is whether you can explain how your own software arrived at an individual shopper's offer.

The announcement describes a Section 6(b) study. It is not a finding that recipients broke the law, and it imposes no new pricing rule on other stores.

This follows the FTC's earlier proposal on personalized-price disclosures. The new element is compulsory information gathering from businesses that actually set customer prices.

Who Received Orders and What They Cover

The recipients also include Instacart, DoorDash, Uber, Lyft, Delta, United, and JetBlue. Each has 45 days from receiving its order to respond, which is recipient-specific rather than a December compliance date for anyone else.

Reuters confirmed the inquiry and reported that Delta, JetBlue, and Instacart denied engaging in personalized pricing.

Those denials belong in the picture. Being asked for information is not proof of the practice under examination.

Sellers should also resist treating every price difference as evidence of a hidden customer profile. A geographic delivery charge, a published business discount, and an offer generated from browsing history produce different checkout totals for different reasons.

Try Reconstructing One Transaction

Rather than starting from a general assurance that your store uses standard pricing, pick one recent discounted order and trace the offer from first advertisement or email through final payment.

Record the displayed product price, coupon, shipping charge, and every other adjustment. Identify which system made each decision, because your storefront, email platform, loyalty app, and testing software can all touch the same order.

Then ask your vendor for an explanation you can check against the transaction. “Our algorithm optimizes conversion” describes a product, not why this customer received this price.

A useful answer names the rule or model version, the data categories it used, and the offer it produced. It should also separate a rule your staff selected from a decision the system generated on its own.

Test Differences Without Assuming Wrongdoing

Build a controlled comparison around one product. Hold variant, currency, delivery address, and testing time constant, then compare the customer states your business actually supports, such as a signed-out shopper and a loyalty member.

If totals differ, investigate one variable at a time. A coupon attached to an account is different from a changed base price, and a tax calculation is different from either.

Do not turn a few screenshots into an allegation about a vendor. Preserve the evidence, ask what produced the difference, and repeat the test after resolving obvious causes.

That discipline also protects your team from unnecessary changes. Disabling a legitimate promotion because someone saw a different total reduces sales without addressing the concern.

Put Evidence Requirements Into Vendor Decisions

For a new pricing tool, ask how long decision records stay available and whether you can export them. Find out what happens when the vendor changes its model or you cancel the subscription.

Include the cost of investigating disputed prices when comparing software. A tool that delivers a small conversion improvement but cannot explain its offers generates work for support, finance, and legal.

Use aggregated or minimized data for internal testing where you can. Do not build an unnecessary database of sensitive shopper information just to document pricing, and have counsel review the practices and disclosures that apply to your business.

The developments worth watching are the FTC's findings and any separate action on the earlier proposal. For now, assign one owner to produce a complete explanation of a real discounted order.

If your team cannot reproduce the price from its own records, close that gap before expanding the same pricing system across your catalog.