SkuSync Documentation

Use SkuSync to convert Shopify and SHOPLINE CSV or SHOPLINE 1.0 XLSX product exports, review JSON Schema validation rules, llms.txt summaries, and NDJSON records, and prepare imports between Shopify and SHOPLINE. This guide also explains AI Readiness Checker signals and how to deploy downloaded files.

1 Getting Started

For JSON Schema, llms.txt, and NDJSON, start with the SkuSync product file converter. For store migration, use the import guides below.

AI Readiness Checker

The AI Readiness Checker requests a website's public files and markup through an external scanning service. It checks technical signals, not AI mentions, citations, recommendations, search rankings, or traffic.

Signals and limits

• llms.txt: checks for a Markdown site summary using the proposed convention. Its presence does not establish adoption by an AI service.
• Schema.org: looks for page markup describing products. This is separate from SkuSync's downloaded JSON Schema validation rules.
• NDJSON: looks for machine-readable product records at checked locations. A feed at another location may not be detected.
• robots.txt: checks crawler instructions. A file's presence does not prove that every crawler is allowed or follows those instructions.
• Sitemap: checks a URL discovery signal. A sitemap does not guarantee crawling or indexing.

Run a check and interpret the result

1. Open the checker and enter a public website URL. The URL is sent to the external scanning service.
2. Select Analyze and wait for the request to finish.
3. Review each signal and the tool-specific readiness score from 0 to 100. Discovery, Structure, and Machine Readability summarize the detected signals.
4. Verify reported issues on the site itself. Access restrictions, redirects, timeouts, or untested file locations can limit the scan. Unknown or unavailable results are not proof that a file is absent.
5. Review and deploy any changes yourself, then scan again. SkuSync does not publish files or add Schema.org markup to your store.

The score is a diagnostic summary, not a validated measure of AI visibility or a ranking forecast. See the implementation references and file deployment notes.

AI Readiness Checker: Implementation References

These examples are implementation references, not automatically generated or deployed by the checker. Replace placeholders with verified site data, choose crawler permissions deliberately, and validate each file before publishing. Example NDJSON does not certify a destination feed. Add JSON-LD to pages separately; SkuSync JSON Schema is a validation rule file.

# Brand / Site Name

## Docs
- [About](https://example.com/about): Company overview
- [Policies](https://example.com/policies): Policy index

## Products
- [Catalog](https://example.com/products): Product index

# Brand Long-form Context

## Policies
...

## Product Knowledge
...

## Support FAQ
...

{"item_id":"SKU-1","title":"Demo Product","description":"Short product summary","url":"https://example.com/products/demo","brand":"Brand","seller_name":"Store","seller_url":"https://example.com","is_eligible_search":true}
{"item_id":"SKU-2","title":"Demo Product 2","description":"Short product summary","url":"https://example.com/products/demo-2","brand":"Brand","seller_name":"Store","seller_url":"https://example.com","is_eligible_search":true}

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Brand Updates</title>
    <link>https://example.com</link>
    <description>Latest updates</description>
  </channel>
</rss>

User-agent: *
Allow: /
Sitemap: https://example.com/sitemap.xml

User-agent: Google-Extended
Allow: /

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/products/demo</loc>
    <lastmod>2026-03-01T09:00:00Z</lastmod>
  </url>
</urlset>

<meta name="robots" content="index,follow,max-snippet:160,max-image-preview:large" />
X-Robots-Tag: index, follow, max-snippet:160

<link rel="canonical" href="https://example.com/products/demo" />
<link rel="alternate" hreflang="en-US" href="https://example.com/en/products/demo" />
<link rel="alternate" hreflang="fr-FR" href="https://example.com/fr/products/demo" />
<meta property="og:title" content="Demo Product" />
<meta property="og:description" content="Demo summary" />
<meta property="og:image" content="https://example.com/og.jpg" />
<meta name="twitter:card" content="summary_large_image" />

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Brand"
}
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to choose a product"
}

/* TEAM */
Team: Brand Team
Contact: [email protected]

/* SITE */
Language: en-US
Standards: HTML5, JSON-LD

Contact: mailto:[email protected]
Expires: 2027-12-31T23:59:59Z
Preferred-Languages: en, zh

Shopify & SHOPLINE CSV/XLSX Structure

SkuSync detects Shopify and SHOPLINE 2.0 CSV headers and SHOPLINE 1.0 XLSX headers. Preserve the original column names and confirm the platform in the preview. SHOPLINE 1.0 exports may lack image URLs, so check image data separately.

Handle,Title,Body (HTML),Vendor,Variant Price,Image Src
classic-tee,"Classic Cotton Tee","<p>100% organic cotton</p>",BrandX,29.99,https://.../tee.jpg
slim-jeans,"Slim Fit Denim","<p>Indigo wash</p>",BrandX,89.00,https://.../jeans.jpg

3 Format Specifications

# Product Catalog Context
## Classic Cotton Tee
ID: 10234
Price: $29.99
Description: 100% organic cotton, pre-shrunk, available in earth tones.
## Slim Fit Denim
ID: 10235
...

Usage Guide: Review and Deploy Outputs

1. In SkuSync, enter the correct store URL before uploading product files so generated links use the intended domain.
2. Review the detected format and source preview. Download JSON Schema, llms.txt, NDJSON, or the ZIP archive.
3. Use JSON Schema as validation rules in a compatible validator. Inspect the actual NDJSON records separately; do not assume all fields or defaults meet the destination's requirements.
4. Check product links, image URLs, prices, currency, stock, identifiers, and variants. Validate any feed against its destination's current rules before submission. SkuSync does not guarantee compliance or approval.
5. To publish llms.txt and NDJSON, upload them to hosting you control and expose public file URLs. Verify the response contains the file content, not an error page or login page. Review access rules and refresh the files when catalog data changes.
6. Add Schema.org Product markup to product pages separately if needed. A JSON Schema download does not create this markup.

SkuSync does not deploy files, submit feeds, or schedule catalog synchronization. For SHOPLINE 2.0 hosting, see root file deployment. For migration, follow the two import guides below.

Import SHOPLINE CSV or SHOPLINE 1.0 XLSX into Shopify

Use the SHOPLINE to Shopify CSV converter for SHOPLINE 2.0 CSV or SHOPLINE 1.0 XLSX product exports.

1. Export products from SHOPLINE and keep the original headers. Save a backup of the source and any existing Shopify catalog.
2. Upload the CSV or XLSX in the converter. Confirm the detected platform and review the field mapping, sample values, product count, and variants.
3. Download the Shopify CSV. Review handles, SKU values, variant options, prices, inventory, and image URLs. Check repeated handles against existing Shopify products before choosing any overwrite option.
4. In Shopify admin, open Products, then Import, and select the converted CSV. Review the import preview and settings before confirming; try a small batch first.
5. Check imported products, variants, inventory, and images. SHOPLINE 2.0 image URLs must stay accessible during import. SHOPLINE 1.0 XLSX exports do not provide image URLs; add missing images separately.

This is a product file conversion. Review destination requirements and import results; the file does not migrate orders, customers, themes, or store settings. For the reverse direction, see Shopify to SHOPLINE 1.0.

Import Shopify CSV into SHOPLINE 1.0 as XLSX

Use the Shopify CSV to SHOPLINE 1.0 XLSX converter. This output targets the SHOPLINE 1.0 template, not SHOPLINE 2.0 CSV import.

1. In Shopify admin, open Products, then Export, and download a product CSV. Preserve standard headers such as Handle, Title, Variant SKU, and Variant Price.
2. Upload the CSV in the converter. Review the field mapping, sample values, product count, variant rows, and image count.
3. Download the SHOPLINE 1.0 XLSX. Compare it with the template accepted by your store and review names, options, SKU, quantity, price, weight, barcode, and image URLs.
4. In SHOPLINE 1.0 admin, open the product bulk import workflow, select the XLSX file, and review any validation messages before confirming. Begin with a small sample and keep a backup before updating existing products.
5. Inspect the imported products and variants. Image URLs must be publicly accessible; correct missing images, stock, or other destination-specific fields before importing the rest of the catalog.

The converter prepares a workbook locally and does not connect to your store or run the import. For the reverse direction, see SHOPLINE to Shopify.

folder SHOPLINE 2.0: Publish txt / NDJSON Files at Root Paths

The community tutorial below shows how to upload a text file and redirect a root path to its hosted URL. For downloaded llms.txt or NDJSON files, verify that your store accepts the file type and serves the intended content. Check the final response and redirects; this is a deployment step you perform after downloading.

1. Upload the text file in the admin

Navigate to Settings -> File library -> Upload file -> Add file. The screenshots show the Chinese admin interface.

2. Copy the hosted file URL

3. Redirect the root path to the hosted file URL

Before configuring the redirect:

• For multiple domains, verify the root file path on each domain after setting the redirect.
• Use the full hosted file URL as the redirect destination, then check that the redirect resolves to the file.

3.1. Open Domains -> Redirects -> Manage redirects

3.2. Add a redirect from the root file path (for example, /llms.txt) to the URL copied in step 2

5 Best Practices

Troubleshooting