Direct answer
To add a manual, specification sheet, warranty, or care guide to a WooCommerce product, store the file in the WordPress Media Library, save its attachment ID on the product, and render one escaped link through WooCommerce's native single-product summary hook. If the attachment or URL is missing, show nothing. Do not guess a filesystem path, copy the file, replace the product template, or claim the public Media Library URL is private.
StoreFixKit's Product Documents for WooCommerce follows that narrow model. Free adds one file to one product. Pro adds bounded product-specific files and one reusable category document set.
A document link is not a protected download system
A normal WordPress Media Library attachment has a public URL. Adding that link to a product makes discovery easier; it does not create authentication or authorization.
That distinction matters. These files are usually appropriate for a public product page:
- user manuals;
- public specification sheets;
- assembly instructions;
- care guides;
- warranty terms intended for every shopper;
- public safety or compliance documents supplied by the merchant.
These jobs need a different system:
- purchased-only software downloads;
- customer invoices;
- account-specific documents;
- confidential service files;
- expiring or signed links;
- files that require role, region, or legal access controls.
A focused product-document plugin should say this clearly instead of turning one link into an unsupported security promise.
Store an attachment ID, not an arbitrary URL
WordPress already owns uploads, Media Library records, MIME checks, and attachment URLs. Saving the attachment ID lets the plugin ask WordPress whether the record still exists and whether WordPress can supply a URL.
An arbitrary URL field looks flexible but expands the failure surface. It can point to an untrusted domain, an expired temporary URL, an unsafe protocol, or a file the site owner no longer controls. A server-path field is worse because public requests should never guess or expose local filesystem locations.
The WooCommerce developer guide for adding product fields demonstrates the normal product-data pattern: add an owned field through WooCommerce's admin hooks and save only authorized, sanitized data. The same principle applies to an attachment reference.
Use a native summary hook instead of a product tab
Product tabs depend on a template containing the tab area. Blockified product templates and customized themes may arrange the page differently.
A public support complaint reported that WooCommerce 10 changes left a free attachment plugin without a useful non-tab placement. Another merchant reported that an attachment tab did not display even with a default theme. Individual reports do not prove one universal defect, but they make placement ownership a release requirement.
The native woocommerce_single_product_summary hook provides a smaller contract than replacing a product template or forcing a tab. If a custom theme removes that hook, a one-job plugin should remain silent and document the boundary. Injecting CSS selectors or rewriting templates to force placement would create a much larger compatibility burden.
Missing files should remove one link, not break the product
An attachment can be deleted, trashed, moved by another system, or left without a usable URL. A public support report describes an attached PDF that reloaded the product page instead of opening the file. The visible symptom may have several causes, but the safe plugin response is straightforward:
- validate that the saved value is a positive attachment ID;
- confirm the record is still an attachment;
- ask WordPress for its attachment URL;
- render an escaped link only when all three checks pass;
- otherwise return without output or a storefront write.
Do not redirect to the product, search the filesystem, select a similarly named file, or rewrite the product during a visitor request. Silence is the reversible failure mode.
Keep the link label plain and bounded
The link needs useful words such as Download user manual or Warranty information. Plain text with a short character limit is enough.
Allowing arbitrary HTML, shortcodes, buttons, scripts, or embedded forms would turn one document label into a content-rendering system. It would also make escaping, accessibility, theme compatibility, and WordPress.org review more difficult.
When the merchant leaves the label empty, the Media Library title can provide a sensible fallback. A final translated Product document fallback prevents a blank link.
Multiple documents need one visible order
Once a store has several files, precedence must remain understandable. A bounded model can use this order:
- the Free product document;
- additional documents explicitly saved on the product;
- reusable documents assigned through a matching product category;
- duplicates removed by attachment ID.
Product exceptions and one product-level category opt-out are enough to handle the common case without creating a condition builder. The list can be capped at 20 unique attachments so one product page cannot accidentally become an unbounded file index.
The current WooCommerce Product Documents and Attachments offer confirms that merchants pay for document workflows. That is category evidence, not proof that every store needs every feature or that a new plugin will reach a particular revenue target.
Do not delete customer media on uninstall
The plugin owns references, not the underlying files. Removing a document from a product or uninstalling the plugin should delete only its product metadata and bounded rule options.
It should never delete:
- the attachment post;
- the physical upload;
- the product;
- product prices or stock;
- historical orders;
- unrelated WordPress options.
This ownership boundary also makes rollback simpler. Deactivate the plugin and only its links disappear; WordPress and WooCommerce data remain available for a previous version or another tool.
Resource and privacy boundary
A product page already contains the product object. The plugin can read one saved attachment ID, perform one attachment lookup, and render no frontend asset.
It needs no:
- custom database table;
- cron job;
- product scan;
- frontend JavaScript or stylesheet;
- customer cookie;
- telemetry;
- StoreFixKit request from the public product page.
The Pro license service belongs only to authenticated admin activation and update checks. A license outage must not remove the complete one-document Free result.
StoreFixKit's Product Documents documentation includes screenshots, exact setup, public-file warnings, troubleshooting, rollback, uninstall ownership, and the support evidence checklist.
Beginner launch checklist
One valid file
Choose an existing Media Library attachment, save the product, open the product page privately, and follow the link.
Empty label
Remove the custom label. Confirm the attachment title or translated fallback produces a readable link.
Deleted attachment
Use a disposable test attachment, remove it from the Media Library, and confirm the product remains usable with no broken document section.
Theme placement
Test the live theme's native single-product template. Confirm the summary hook exists and the document section does not overlap price, description, stock, or cart controls.
Mobile layout
Open the product on a narrow viewport. Long document labels should wrap without creating horizontal overflow.
Pro order and exceptions
Test one Free file, two product-specific Pro files, one category file, one duplicate, one category exception, and one product opt-out.
Deactivation and uninstall
Deactivate Pro and confirm the Free file remains. Deactivate Free and confirm the product remains usable. On a staging copy, uninstall both and confirm the Media Library files and historical orders remain.
Security and support evidence
Only a user allowed to edit the product should save its attachment. Category defaults should require WooCommerce management capability. Every write needs a nonce, capability check, bounded sanitization, and escaped output. WordPress's common plugin issues document the review expectations around validation, sanitization, escaping, and data ownership.
Useful support evidence includes the product ID, attachment ID, attachment type, exact URL, WordPress and WooCommerce versions, plugin versions, theme, cache/CDN, expected result, actual result, and screenshots. Remove credentials, private files, customer data, payment information, and full license keys.
FAQ
Can a product document be private?
Not with this focused release. It links to an ordinary WordPress Media Library URL.
Does removing a link delete the file?
No. The plugin owns only the product reference.
Can it add files to order emails or My Account?
No. Product-page documents, email attachments, and purchased downloads are separate jobs.
What happens when an attachment is deleted?
The link disappears and the product page continues normally.
What happens when Pro expires?
The single Free product document continues locally. Additional product and category documents require an active product-bound license.
Focused plugin
Use the one-job implementation.
Add approved Media Library manuals, specifications, warranties, or care guides to WooCommerce products without editing templates or deleting customer files.