Pepperfry is an Indian online marketplace for furniture and home products. Unlike most platforms in this batch it genuinely has a third-party seller programme: merchants list furniture, decor, lighting, kitchenware and home improvement goods, and Pepperfry handles discovery, a large part of the logistics and the customer relationship. What it does not have is a public developer portal. Sellers work in a merchant portal, and brands that want automated listing, inventory and order sync connect through an order management aggregator rather than directly.
At a glance
What it is
Pepperfry sells furniture and home goods across India, combining an online catalogue with physical experience centres where shoppers can see large items before buying. Furniture is an unusual category to run as a pure marketplace: units are bulky, damage rates are high, assembly is often required and returns are expensive, so Pepperfry has historically taken more of the logistics chain in house than a horizontal marketplace would. For a seller that means Pepperfry is closer to a managed marketplace than to a listing board: it influences fulfilment, delivery and installation rather than simply passing an order through.
The seller base is a mix of manufacturers in furniture clusters, importers, and home and decor brands. Pepperfry is a marketplace in the sense that matters for a connector: the seller owns the listing, sets a price within Pepperfry's rules and gets paid a settlement net of commission, rather than selling stock outright to Pepperfry.
API access
No public developer portal, API reference, SDK, Postman collection or sandbox was found.
The fetcher was blocked throughout. Every path on www.pepperfry.com returned HTTP 403 on 2026-09-21, including the root and the seller landing pages, which indicates an edge bot filter rather than a missing page. The merchant host merchant.pepperfry.com does resolve and served a page titled simply "Merchant", but its content is client rendered and its login path also returned 403. So the merchant portal's existence is confirmed and its contents are not.
The one solid external signal is that Unicommerce lists Pepperfry in its published integrations catalogue, alongside its description of Pepperfry as an online store for furniture, home decor and lamps. An aggregator only ships and lists a connector when it has a working credential path, so a machine-readable seller connection exists even though Pepperfry does not document it publicly.
Getting a seller account
The onboarding route is a merchant application followed by catalogue and quality review, then portal credentials. Pepperfry's published requirements could not be read because of the 403, so no document list, commission rate or fee schedule is stated here. Expect the standard Indian marketplace set: GSTIN, PAN, bank account, a signed seller agreement and category-specific quality requirements, which in furniture usually include packaging standards because damage in transit is the category's main cost.
Before designing a connector, establish which fulfilment lane the seller is on. Pepperfry has run both seller-shipped and Pepperfry-handled models, and the two produce very different shipments rows: in one the seller picks the carrier and owns the tracking, in the other Pepperfry does and the seller only sees a pickup request and a status. Get this from the account manager, not from a help article.
Authentication
Not published. Merchant portal access is a username and password. No API key issuance, token endpoint, header name, scope model or lifetime is documented, and none is invented here. Where an aggregator connects, it holds whatever credential Pepperfry issues on the seller's behalf and your systems authenticate to the aggregator instead.
Objects we can read
Nothing through a documented Pepperfry interface. Inside the merchant portal a seller sees the normal marketplace set, and these are the objects to ask about when specifying an aggregator connection:
- Orders and order items. Pepperfry order number, SKU, quantity, price, order status through the fulfilment lifecycle.
- Listings. The seller's products with Pepperfry product identifiers, price, MRP, status and category attributes.
- Inventory. Quantity available per SKU, held against the seller's own warehouse.
- Shipments. Pickup, dispatch, in-transit and delivery status, plus installation where the category requires it.
- Returns and cancellations. Category-heavy in furniture, and worth a first-class table.
- Settlements. Payouts net of commission, shipping recovery and any damage or penalty deduction.
No sample response is published, so none is given. Anything claiming to be a Pepperfry field name without a published schema behind it should be treated as invented.
Writing back: listings, price and stock
Writes are possible, but not through a documented direct API. The two real routes:
- Merchant portal. Manual listing creation and bulk upload templates, plus price and stock edits. This is the route every Pepperfry seller starts on and it is adequate for a small catalogue.
- Aggregator connector. Unicommerce, and likely other Indian order management platforms, sync catalogue, price, inventory and order status to Pepperfry on the seller's behalf. This is the route to use for anything at scale, and it is the only one with published evidence of existing.
Batch sizes, template formats, processing report behaviour and per-call limits are all unpublished because the portal could not be read.
Webhooks and notifications
None published. Without a direct API, the cadence question resolves to the aggregator's polling behaviour. If the connection is portal only, order notification is by email and dashboard, and the operational risk is dispatch service level breaches from late detection, which in furniture carry penalties.
Rate limits and pagination
Not published.
Mapping to the unified model
Provisional. Platform field names are deliberately left blank rather than guessed.
Gaps and open questions
- www.pepperfry.com returned HTTP 403 on every path, so no Pepperfry-published statement backs this page. Re-fetch with a browser-based client.
- Commission rates, fee schedule and payment cycle are unverified.
- Whether Pepperfry offers any direct API to large sellers, or only portal and aggregator access, is unverified.
- The fulfilment lanes currently on offer, and which one a new seller lands on, are unverified.
- Whether Pepperfry exposes bulk upload templates with a processing report, which would be the pragmatic write path, is unverified.
- Web search was unavailable for this page, so no news coverage or help-centre article was reviewed.
Sources
- unicommerce.com/integrations (Pepperfry listed as a supported channel, read 2026-09-21)
- merchant.pepperfry.com (merchant portal host resolves, page titled "Merchant", content not readable, 2026-09-21)
- pepperfry.com (HTTP 403 to the fetcher on all paths tried, 2026-09-21)