Product Documents
Product Documents: setup guide
Recorded on version 1.0.4 · Narrated walkthrough · English captions
Jump to a chapter 8 chapters
Read the full video transcript
Product Documents 1.0.4 — Magento Admin setup 00:00:00 — Set up Product Documents Welcome to the Agentic Ecom Product Documents Admin guide. We'll walk through the main setup screens and the checks to make before using the module. This guide assumes the extension is already installed. 00:00:13 — Open settings and choose scope Start in Magento Admin and open Stores, Configuration. Choose Product Documents. Check the Scope selector before editing. Use the appropriate website or store view where the setting supports it. The screen values here are a demonstration; enter the settings and service details that belong to your own store. 00:00:33 — Choose the document presentation In Display Settings, choose whether documents appear as a product tab or an inline section. Set the tab name, then choose whether to show the file type icon, description, file size and download count. Use the presentation that makes manuals and datasheets easy to find on your product pages. 00:00:53 — Set upload limits Review Allowed File Extensions and Max File Size before uploading. Allow only the document types your customers need. New uploads are limited to twenty megabytes, and the configured or server limit can be lower. Files in the module's media folder are public by URL; these settings do not create private file storage. 00:01:14 — Add and assign a document Open Catalog, Product Documents, Manage Documents and add a document. Enter a clear title and description. Upload a file or supply an external H T T P or H T T P S URL. Assign the relevant product S K U values, store views and customer groups, then check the active status and sort order before saving. 00:01:37 — Verify the customer view After saving, reopen the document and confirm its product assignments. Check a product page in the intended store view and customer group. Visibility settings filter the module's listings and tracked download route, but anyone who knows an uploaded media URL can still access that file. Use separate protected delivery for confidential documents. 00:01:59 — Save and verify your setup When your required settings are complete, use the screen's Save control and wait for Magento's confirmation. Then reopen the record or configuration and check the saved values at the intended scope. If the storefront still shows earlier settings, refresh the relevant caches. Test your own configuration before using it with customers. 00:02:21 — Your setup checklist That's the Admin setup walkthrough for Product Documents. Check permissions and scope, review the module-specific settings, then save and verify a small staging example. Use the written guide at user guides dot Agentic Ecom dot net for installation details, complete field references and any separate storefront integration steps.
Product Documents 1.0.4 attaches reusable files or external links to products. It displays applicable documents on Luma product pages and exposes document metadata through GraphQL for headless storefronts. Its Admin configuration now opens without AgenticEcom Core.

Install
Section titled “Install”Get your licence key from My Licences, then run:
composer config repositories.agenticecom composer https://repo.agenticecom.netcomposer config --global --auth http-basic.repo.agenticecom.net <YOUR-LICENCE-KEY> xcomposer require agenticecom/module-product-docs:^1.0.5php bin/magento setup:upgradephp bin/magento setup:di:compilephp bin/magento cache:flushVersion 1.0.4 was installed, upgraded and compiled on Magento Open Source 2.4.9 with PHP 8.5.10 without Core. Its Admin configuration page, save and ACL checks passed. Test other editions, versions, themes and media configurations in staging.
Configure and add documents
Section titled “Configure and add documents”- In Magento Admin, open Stores → Configuration → AgenticEcom Product Documents → Product Documents and choose a Luma display position: product tab or inline section. Configure the tab title and the optional badge, description, size and download-count fields.
- Open Catalog → Product Documents and add a document. Enter its title, description, type and sort order. Upload a file or enter an external HTTP(S) URL.
- Assign one or more product SKUs. Choose active status, store views and customer groups that should see the document in module-generated listings.
- Save and check a product page in the intended store view and customer group. Luma links use a tracked route that rechecks the document’s settings before redirecting.

Uploads can use a configured subset of PDF, Word, Excel, PowerPoint, ZIP and supported CAD extensions. New uploads are capped at 20 MB; your configured or server limit may be lower. External links must use HTTP or HTTPS.
Headless storefront
Section titled “Headless storefront”{ productDocuments(product_id: 2041) { doc_id title description file_url file_type file_size doc_type sort_order download_count }}The query filters active documents to the current store and customer group. It returns URLs, which must still be treated as public URLs.
mutation { trackDocumentDownload(doc_id: 39) }Call this mutation after a storefront download to increment the count for a document visible to that customer. Direct visits to media or external URLs are not counted automatically.
CSV import
Section titled “CSV import”Use sku,pdf_file with optional title,doc_type. The named file must already be under pub/media/productdocs. Missing, unsupported and outside-directory paths are skipped and reported. Import into a staging store first to check SKU and file mappings.
Version 1.0.4
Section titled “Version 1.0.4”Defines its own Admin configuration tab for a standalone Composer install. The 1.0.3 document presentation and GraphQL features remain available.
Version 1.0.3
Section titled “Version 1.0.3”This release adds the Luma tab and inline presentation, a visibility-checked tracked link, URL-only records, and stricter upload and CSV path validation. It also applies store and customer-group checks to GraphQL download counting. It does not add private file storage.