Independent source guide

Poshmark listing data: seller fields, offers and reports

A field guide to Poshmark seller listings, SKU and UPC distinctions, private offers, bundle orders, seller reports, and posted limits on automated collection.

Poshmark listings are seller-created item records

Poshmark describes its service as a social marketplace where users list and sell items to one another. Its listing help names title, description, category, size, original price and listing price; other guidance refers to brand, color, condition, material and measurements. These are seller-entered attributes for individual items, not a shared retailer catalog.

Scroll to compare →

Poshmark listings are seller-created item records
Listing layerPoshmark-documented fieldsInterpretation
MarketplacePoshmark, Inc. operates the service; buyers and sellers transact with one another.Poshmark is the marketplace, not the manufacturer or seller of every item.
Listing identityTitle, description and seller’s individual item listing.Similar brand/style text does not establish that two sellers offer the same physical item.
Category and audienceDepartment, category, subcategory and size labels.These organize seller listings; they are not a universal product taxonomy.
Seller-entered attributesBrand, color, condition, material and measurements when supplied.Preserve as seller claims and keep them attached to the individual listing.
QuantityA listing may represent one item or multiple available units.Quantity belongs to the seller’s listing state; it is not another catalog product by itself.

A seller SKU and a UPC or GTIN identify different layers

Poshmark’s seller documentation distinguishes an inventory code assigned by the seller from manufacturer-issued product identifiers. Keep the seller’s closet-level reference separate from any identifier embedded on a retail item.

Identifier scope

Identifier scope
Identifier or fieldSource meaningBoundary
Seller SKUA seller-assigned inventory code for an item in that seller’s closet.It is not a marketplace-wide key and should not be matched across sellers without independent evidence.
ProductID / UPC / GTINThe seller template describes UPC or GTIN as identifiers created by the original manufacturer.Do not relabel this as the seller’s SKU or assume every listing supplies it.
Brand and styleSeller-entered brand and item-description text.Text similarity alone does not prove a shared manufacturer model.
Size and quantityListing-level size and available units.Keep the item’s selected size and quantity together; do not invent a product-family or variant ID.
Unlabeled identifiersA code or number without a source-defined meaning.Leave it unattributed rather than assigning an ID type.

Condition and fit details remain seller claims

Poshmark’s listing guidance encourages sellers to describe condition, material and measurements, while its Terms place responsibility for listing content on the seller. Treat those details as attributed listing evidence rather than verified product specifications.

What a listing detail can support

What a listing detail can support
Listing detailHow to describe itWhat it does not establish
ConditionThe condition selected or described by the seller at listing time.A standardized inspection grade across closets.
Measurements and fitMeasurements or fit notes the seller chose to provide.Consistent fit across brands, categories or sellers.
Material and descriptionSeller-authored item text and labels.Manufacturer-verified composition or care instructions.
Photos and visible labelsThe listing contains seller-posted image evidence.Permission to copy, republish or reuse the image or its embedded personal details.
Authenticity-related claimsA seller’s own statement, or any separately labeled marketplace process.Independent verification based only on a description, code or photo.

An asking price, a private offer and an order price are separate events

Poshmark’s help distinguishes the public listing price from private buyer-seller offers. It says offers and counteroffers are visible to those parties, and that a sold listing reflects the final order price. A price record needs its event type and observation context.

Price-event relationship

Price-event relationship
EventSource contextHow to keep it distinct
Original priceSeller-entered reference price on a listing.Keep it separate from the current asking price.
Listing priceThe seller’s public asking price at the time shown.It is not necessarily the accepted offer or final order amount.
Offer or counterofferPrivate negotiation between the buyer and seller.Do not infer private offers from a public listing or treat an offer as a sale.
Final order priceThe final amount reflected on a sold listing, according to Poshmark’s offer help.Keep this tied to the completed order event, not a prior ask.
Offer status and timingAn offer can remain pending, be accepted, declined or expire under the help-page rules.These states change; date any source observation and do not present them as fixed listing attributes.

A bundle joins listings from one seller under an order relationship

Poshmark defines a bundle as multiple listings from the same closet. Its seller-report documentation keeps the included listings identifiable while linking them to a shared order; a bundle is therefore an order relationship, not a replacement product record.

Bundle and order fields

Bundle and order fields
RecordDocumented relationshipModeling boundary
Included listingEach bundle contains one or more seller listings.Retain each listing’s own size, quantity and seller-authored attributes.
Bundle orderThe transaction groups items from one seller’s closet.Do not collapse the included listings into a single new product.
Shared order identifierThe Sales Report can show bundled listing rows together under a shared Order ID.Keep the identifier account-scoped and never expose buyer or seller identity.
Order priceThe Sales Report describes the final sale amount for a listing, including a listing within a bundle.Use the report’s own per-listing order-price definition; do not assign a bundle total to every item.
Discount and shipping contextAn offer or bundle may include seller-side discounts or shipping context.Keep discounts and shipping attached to their source order/offer fields.

Seller reports and posted rules set the data boundary

Poshmark documents Inventory and Sales Reports as tools for a seller’s own closet. They can contain private business fields, while the current Terms and robots file set separate boundaries for the Service. This reference describes those source statements without treating visibility or crawler directives as authorization.

Report scope and source boundaries reviewed 2026-10-07

Report scope and source boundaries reviewed 2026-10-07
EvidenceWhat Poshmark documentsBoundary for this reference
My Inventory ReportAvailable listings for the account owner; fields may include days listed, seller SKU, optional cost price, lowest/current listing price, units, size and private listing fields.Describe only as the seller’s own account report; exclude cost, private fields and account data from a public catalog.
My Sales ReportSeller-owned order details, including order price, offer/buy-now status and bundle relationships.Do not include transaction parties, earnings, contact details or private exports.
Terms date labelsThe Legal Center version banner says June 3, 2025; its embedded Terms body says October 3, 2024.Retain the observed discrepancy and review date; do not infer a controlling date or offer a legal conclusion.
Terms contentSection 4(b) prohibits automated collection for the Service and harvesting information from Poshmark systems; §§6–7 address user content and copying.Attribute the Terms and do not provide collection instructions or imply permission.
Robots directivesThe public file checked on 2026-10-07 disallows paths including /listings, /search, /api and user/action routes.Robots.txt is a crawler directive, not authorization.
Public API/feed evidenceThe reviewed help and Terms describe listing pages and seller-account reports.These pages do not establish a Poshmark catalog API/feed or permission to collect; no existence or absence claim is made.

Content reviewed 2026-10-07.