> ## Documentation Index
> Fetch the complete documentation index at: https://docs.skutap.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How skutap works

> One record per product, from supplier catalogues to retailer systems.

Music suppliers send product data in every shape: spreadsheets with different columns, header rows that move, prices typed as text. Every retailer who stocks the product cleans the same data again before it reaches a website, POS or ERP.

skutap does that work once. A supplier's catalogue comes in once and becomes one record per product. Each retailer takes it out in the shape their own system expects.

## For suppliers

<Steps>
  <Step title="Import a catalogue">
    Upload a CSV or Excel file. It is read through a saved map that matches its columns, and each
    row becomes a product record.
  </Step>

  <Step title="Categorise products">
    Every product is placed in the skutap category tree. Suggestions arrive after each import, and
    anything not applied automatically waits for review.
  </Step>

  <Step title="Publish to retailers">
    A product reaches retailers when it is active, published and categorised. Uncategorised products
    are held back until they have a category.
  </Step>

  <Step title="Share the catalogue">
    Invite retailers to see the published catalogue. A feed link gives anyone a CSV of it that is
    current every time it is opened, and a feed can be emailed to retailers who don't use skutap.
  </Step>
</Steps>

## For retailers

<Steps>
  <Step title="Accept an invitation">
    A supplier invites the retailer. Once the invitation is accepted, that supplier's published
    products appear in the catalogue.
  </Step>

  <Step title="Browse products">
    Filter the catalogue by supplier, brand and category. Products changed since the last export are
    marked.
  </Step>

  <Step title="Export">
    Export products as a CSV laid out for the system it is going into, from a template.
  </Step>
</Steps>

## Every run is on record

Each import and export is a run that stays open to inspect afterwards: what came in, what was produced, and what failed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.