POM Tweaks for developers

This chapter documents the supported public integration surface of POM Tweaks. Use these contracts from a site plugin or child theme without depending on the plugin’s private classes, settings storage, administration requests, or file layout.

Feature-specific interfaces exist only while their corresponding tweak and required dependency are active. Check shortcode_exists() or function_exists() where an integration can run before POM Tweaks loads or while a feature may be disabled. A feature-specific filter simply does not run when its feature is inactive.

Chapter contents

1. Use the supported shortcodes
2. Read a product-specific terms URL
3. Customize llms.txt eligibility
4. Extend WooCommerce PDF catalog generation
5. Use feature hooks
6. Integrate with WooCommerce output safely
7. Inspect tweak status with WP-CLI

These pages cover interfaces intentionally exposed to other WordPress code and the supported read-only WP-CLI status commands. Internal component classes, AJAX actions, option names, migration commands, and administration schemas are not public APIs.

Integration baseline

1. Run integrations after WordPress has loaded plugins.
2. Treat filter inputs as immutable unless the filter explicitly returns a replacement value.
3. Validate object types and return the documented type.
4. Escape output for its final HTML, URL, attribute, or text context.
5. Test with the relevant tweak enabled and disabled.
6. Test without the optional WooCommerce or WooCommerce Bookings dependency when it applies.