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

# Create and Publish Product Specification Documents

> Manage product specification documents in Avstarna: create specs with allergy info, nutrition facts, and microbiological data, then publish for customers.

Product Specifications (SDS) in Avstarna give you a structured, compliant way to document everything about a food or manufactured product — from microbiological safety data to packaging dimensions. Once approved, your specs are published to a public-facing widget that your customers can browse at any time, keeping your business transparent and audit-ready.

## What Is a Product Specification?

A product specification (SDS) is a versioned document attached to a specific product variant. It captures the full technical and safety profile of that variant, ensuring your team, your customers, and any regulatory body have access to accurate, up-to-date information. Each spec is linked to its product variant and carries a version history so you always know what changed and when.

## The Approval Workflow

Every specification moves through a structured workflow before it reaches your customers.

<Steps>
  <Step title="Concept">
    Create a new spec and fill in the required sections. The document is saved as a draft and is not visible to the public.
  </Step>

  <Step title="Review">
    Submit the spec for review. A designated reviewer on your team receives the spec and examines the data for accuracy and completeness.
  </Step>

  <Step title="Approved">
    The reviewer approves the spec, confirming the data is accurate and complete. The spec is now ready to be published.
  </Step>

  <Step title="Rejected">
    If the reviewer finds issues, they reject the spec with a written note explaining what needs to change. The spec returns to **Re-concept** status so you can revise and resubmit.
  </Step>

  <Step title="Published">
    Once approved, publish the spec to make it publicly accessible. It immediately appears on your public product specs widget and receives a shareable public URL.
  </Step>
</Steps>

<Note>
  Published specifications include a legal footer that reads **"Valid on the day of printing"** followed by the print date, keeping your printed documents compliant with labeling regulations.
</Note>

## What Goes Into a Specification

Each SDS is organized into clearly defined sections so nothing gets missed.

<AccordionGroup>
  <Accordion title="Basic Specs">
    General product information that identifies the variant and its intended use, including target user details.
  </Accordion>

  <Accordion title="Microbiological Data">
    Safety test results covering aerobic bacterial count, yeasts and fungi, *B. cereus*, *C. perfringens*, *Campylobacter*, coliforms, *Salmonella* spp., *Listeria monocytogenes*, and *S. aureus*.
  </Accordion>

  <Accordion title="Contaminations Data">
    Records of any contaminant testing relevant to the product, supporting traceability and food safety compliance.
  </Accordion>

  <Accordion title="Nutrition Facts">
    Full nutritional breakdown as required for food labeling, ready to display to consumers.
  </Accordion>

  <Accordion title="Allergy Information">
    Allergen data is inherited directly from the parent product, ensuring consistency across all variants without manual re-entry.
  </Accordion>

  <Accordion title="Packaging & Delivery">
    Foil material, box material, box contents, box weight, box dimensions, order unit, and required delivery temperature — everything a logistics partner or retailer needs.
  </Accordion>
</AccordionGroup>

## The Public Widget

Once you publish a spec, it becomes available on your public product specs page at:

```
/[lang]/[companySlug]/product-specs
```

Your customers and partners can visit this page without logging in to browse all of your published specifications. Each published spec also has its own direct public URL, which you can share in emails, on packaging, or in retailer documentation.

## Version History

Every time you update and republish a specification, Avstarna saves the previous version. You can review the full version history of any spec to see exactly what changed between releases — useful for audits, customer queries, or internal quality reviews.

## Plan Limits

<Note>
  If you are on the **START plan**, you can publish a maximum of **5 product specifications**. Upgrade to the **PRO** or **BUSINESS** plan to create and publish unlimited specs.
</Note>

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Can I edit a spec after it has been published?">
    Yes. Edit the spec and resubmit it through the approval workflow. The updated version is published as a new version, and the previous version is retained in the version history.
  </Accordion>

  <Accordion title="Where do I manage my product specifications?">
    Navigate to **Admin → Product Specs** for a full list of all specs across your products. You can also access the spec for a specific variant directly from the product page.
  </Accordion>

  <Accordion title="Who can approve a specification?">
    Any team member with reviewer permissions can approve or reject a spec. Your account administrator can manage role assignments in your team settings.
  </Accordion>

  <Accordion title="Is allergy data always accurate if I update the parent product?">
    Allergy information is inherited from the parent product at the time the spec is created or updated. If you change allergen data on a product, review and republish any related specs to keep them current.
  </Accordion>
</AccordionGroup>