Full Page Management for Resources

As e-commerce businesses grow, so does the amount of information that supports buying decisions and customer experience.

Return policies change. Product manuals evolve. FAQs, shipping rules, and care guides need updates.

Until now, pages inClerk.io were primarily managed through external feeds. That worked well — but it limited how much control teams had over content that needed quick changes.

This product update introduces full page management in Clerk.io, giving teams more flexibility and ownership.

📄 More Control Over Pages

We’ve now made it possible for you to create, update and delete pages, allowing you to manage documents directly inside Clerk.io.

What you can do now

➕ Create pages manually Upload documents via file upload (PDF, DOCX, HTML, MD, TXT)

✏️ Update existing pages Edit content when policies, manuals, or documentation change

🗑️ Delete pages individually Remove outdated or irrelevant documents with full control

Pages are stored as plain-text documents. They are not website pages and not a CMS — think of them as structured resources your platform can use.

Common examples include:

• Return & refund policies • Shipping information • Product manuals and care guides • Warranty details • FAQs and internal documentation

🔄 How This Works With Existing Page Syncs

Nothing changes for pages that are synced from external feeds.

• • Synced pages continue to update automatically
• • Pages removed from feeds are still cleaned up as before

Manually uploaded pages work differently by design:

• 🔒 They are protected
• 🚫 They are never deleted during sync operations
• ✅ You stay fully in control of them

This gives you flexibility without disrupting existing integrations.

🎯 Why This Update Matters

This update gives teams more control over how content lives inside Clerk.io.

That means:

• Faster updates when information changes • Less dependency on external systems • Cleaner, more intentional document management

It’s a foundational improvement that supports multiple use cases across the platform.

🤖 How This Affects AI Chat (One Key Example)

One important use case for pages isAI Chat .

When Chat has access to pages such as:

• • Return policies • Shipping details • Product manuals • Care instructions …it can use them as trusted resources when answering customer questions.

Example:

A shopper asks about your return policy → Chat detects a relevant document → reads it → answers accurately.

This is not AI training. It’s about giving Chat access to the same information your business already relies on.

The result:

• • More accurate answers • Fewer support hand-offs • Less friction for shoppers • More confidence at decision moments

🚀 A Small Update With Long-Term Impact

This may look like a small feature — but it enables more control, safer content handling, and better alignment between your documentation and your store experience.

As you use more of the Clerk.ioplatform — this ensures the right information is always available where it’s needed.