datawebotTakealot data: product pages, seller offers and the Marketplace API
Compare Takealot products and seller offers; map the private seller API's stock and reporting fields, South African regions and buyer checkout delivery context.
A Takealot product page can represent a shared product with several seller offers
Takealot's Platform Terms say a third-party seller's trading name and “sold by” label appear on its product page, and sellers offering the same product may use different prices or discounts. Treat the product identity and each merchant offer as separate records; a product page does not expose the seller's account report.
Scroll to compare →
| Record level | Public or API context | Keep separate |
|---|---|---|
| Product / TSIN | The product record can be shared by Takealot and multiple seller offers; the Marketplace API calls the product identifier `tsin_id`. | A product identity is not one merchant's stock, price or offer status. |
| Seller offer | The product page may show the seller's trading name and “sold by” label; the seller API uses `offer_id` and merchant SKU. | Price, discount, offer condition and buyable status belong to the specific offer where displayed or returned. |
| Merchant account | Seller Portal/API records cover the authenticated seller's own offers and operations. | A seller API response does not give access to competitor accounts or establish what a shopper sees on every product page. |
The Marketplace API key is seller-account scoped, not a public catalog credential
Takealot's current Marketplace API documentation says seller-specific endpoints require an API key in the `X-API-Key` header. The account owner creates a key in the Seller Portal; one key can be active per seller account, creating a replacement deactivates the previous key, and the key applies to all documented API endpoints for that seller account without separate endpoint scopes.
Scroll to compare →
| API fact | Documented scope | Data boundary |
|---|---|---|
| Authentication | API key required for seller-specific information; the key is associated with the seller account. | Do not expose keys, request credentials or portray this as anonymous product search. |
| Endpoint permissions | The current docs say the key reaches all API endpoints for its associated seller account and has no separate per-endpoint scopes. | Keep the full seller-account authorization boundary in mind when deciding which data to store or share. |
| Key rotation | Only one API key can be active at a time per seller account; generating a new key deactivates the prior one. | Treat keys as account secrets and plan rotation with the account owner. |
| Public shopper pages | The public product page and checkout provide shopper-facing context; the Marketplace API is documented for merchants managing seller information. | Do not infer public access to seller orders, returns, warehouse inventory or performance reports. |
Offer and inventory fields belong to the seller's account record
The current offer API reference documents seller offer identifiers, price/status fields and separate warehouse stock expansions. These values are seller-account data. Keep the original field name, currency, update time and warehouse layer rather than turning them into a public nationwide-stock claim.
Scroll to compare →
| API field or expansion | Documented meaning | Interpretation rule |
|---|---|---|
| `offer_id`, `tsin_id`, `sku`, `barcode` | Seller offer, shared product and seller-assigned identifiers. | Use `tsin_id` for the product relation and `offer_id`/SKU for the merchant's offer; do not join on title alone. |
| `selling_price`, `rrp`, `discount_percentage`, `condition`, `status` | Offer price, recommended retail price, discount, condition and buyability/disable state where returned. | Preserve the API label and South African Rand context; an account offer value is not automatically the buyer checkout total. |
| `page_views_30_days`, conversion percentages | The offer schema includes named seller-performance fields with 30-day windows. | Keep the exact period and seller account; these are not public listing signals or all-time metrics. |
| `seller_warehouse_stock` | Seller-side warehouse quantity information. | Keep warehouse identity and quantity separate from stock held by Takealot. |
| `takealot_warehouse_stock` | Takealot-warehouse stock rows with regional and inventory-state fields such as quantity available, stock on way and receiving. | Retain the documented region; one region's stock is not nationwide availability. |
| Offer charges | The `offer_charges` expansion is deprecated and always empty in the current docs; the API points to a separate charges endpoint. | Do not present an empty deprecated expansion as zero fees or a complete charge calculation. |
Sales, shipments and returns are private seller operations
Takealot's seller API includes account-specific sales, fulfillment, shipment and return records. Its sales fields can carry order and offer identifiers, fees and sales/stock-source regions; return records may include a customer comment. These are not public product-page observations and should remain limited to an authorized seller's business workflow.
Scroll to compare →
| Account record | Documented examples | Public-data boundary |
|---|---|---|
| Sale | Order item, order date/status, offer/product/SKU, selling price, quantity, fees and sales or stock-source region. | Do not expose order IDs, fees or a seller's transaction history as public marketplace data. |
| Shipment / replenishment | Shipment destination region, facility and item quantities/statuses in a seller's operations. | Takealot fulfillment stock is distinct from the seller's on-hand inventory and a shopper's delivery estimate. |
| Return | Seller return IDs, order/offer, region, date, reason, outcome/transactions and `customer_comment` where requested. | Keep customer comments, identifiers and order-level details private; never use them in public examples or competitor datasets. |
South African stock regions and checkout delivery estimates are different signals
The API schema uses South African regions such as CPT, JHB and DBN for seller operations and Takealot warehouse stock. The Platform Terms say delivery estimates vary with the items, payment method and selected delivery or collection location, and that checkout shows the most accurate estimate. Preserve those contexts separately from a product's listed price or seller inventory.
Scroll to compare →
| Signal | Scope | Do not infer |
|---|---|---|
| Seller warehouse stock | A quantity attached to the merchant's own warehouse record. | It does not mean stock is already in Takealot's fulfillment network. |
| Takealot warehouse stock | Regional fulfillment inventory, with states such as available, on the way or in receiving where returned. | A regional row is not a national store count or guaranteed shopper availability. |
| Product-page delivery estimate | A shopper-facing estimate affected by items, payment method and selected location. | It is not a seller API lead time or a guaranteed order date; checkout has the current order estimate. |
| Seller offer price | A merchant's price for a product offer, potentially different from another seller's price for the same product. | It may differ from checkout total, discounts, delivery charges or an account-specific coupon. |
Robots directives and the Platform Terms set separate limits
Takealot's current robots.txt lists a sitemap, allows `/` generally and disallows account/cart/wishlist paths, AJAX/help fragments and numerous filter/sort query patterns. Its Platform Terms separately prohibit robots, spiders, other automatic devices or manual processes used to monitor, copy, distribute or modify the platform or content, except technology used by internet search websites to direct users there; reuse or reproduction of platform content also requires the property owner's written consent. The robots file is not a content license.
Scroll to compare →
| Source | Reviewed statement | Scope |
|---|---|---|
| robots.txt | Sitemap target is listed; root path is generally allowed while account and selected query paths are disallowed. | Crawler directives do not authorize collection, commercial use or republication. |
| Platform Terms | Browse/shop access is distinct from rights to use content; automated and manual monitoring/copying restrictions are stated separately. | Attribute to Takealot's current Platform Terms; do not rewrite them as a specific legal conclusion about every integration. |
| Seller Marketplace API | A documented, seller-authenticated account route for merchant operations. | API documentation does not grant access to other sellers' data or waive content rights for public pages. |
Content reviewed 2026-10-07.