A hardware data feed needs more than product descriptions.
A retailer needs to identify each product, show its specifications and know which accessories fit. These are separate records, even when they arrive through the same API.
What comes from the feed, and what stays in your store
| Data | Example | Owner |
|---|---|---|
| Product identity | Lenovo charger part 0A36258; exact model and aliases | SpecJoin catalogue |
| Connection and power specifications | Computer ports; charger connector and rated output | SpecJoin catalogue |
| Compatibility relationship | ThinkPad X250 + 0A36258, with charging conditions | SpecJoin check |
| Retail offer | Your SKU, price, stock, condition and included parts | Your store |
SpecJoin covers connections, displays and power. It does not supply a complete CPU/RAM/storage catalogue, product photography, live retailer prices or stock.
One real relationship
ThinkPad X250 + Lenovo 0A36258 charger
Lenovo lists this charger for the laptop. Charging speed and performance under heavy use have not been assessed.
- Use the genuine part number shown and the mains connection for your country. Other spare parts and generic chargers need their own compatibility check.
A useful feed preserves both identities and the relationship’s requirements. Flattening this to “compatible = true” would lose the conditions the shopper needs.
GET /api/v1/accessories/chargers?computer_id=lenovo-thinkpad-x250&charger_id=lenovo-psu-0a36258Current data release: 2026-09-23.1. The full response includes sources, scope and version fields.
API or periodic downloads?
| Route | Use it when | What your team does |
|---|---|---|
| API | You need product lookup or a selected compatibility check in an application. | Request from your server; map identities to local products; keep the findings. |
| Periodic downloads | You prefer a scheduled import into your catalogue or internal database. | Import the category-specific tables; retain requirements and the release version. |
Both use the same shared data. Neither is a universal Shopify or marketplace import file. A developer or import tool connects it to your store’s fields.
Keep updates safe
- Map verified manufacturer/model/part identities to your own SKUs. A similar title is not an exact match.
- Keep stock and prices independent. A product missing from a sample is not an instruction to delete it from your store.
- Store the data version with imported findings. Review changed requirements before reusing recommendations.
- Show unknowns as unconfirmed. Show conditional recommendations only with their conditions.
A Google Shopping feed is a different output: it describes your retail offers. Use the manufacturer’s actual MPN there, not a SpecJoin ID or an invented number. Google’s MPN requirements.