Every existing \"Request a Quote\" plugin is a manual form: the customer fills\nfields, a rep drafts the quote back by hand. AI Quotes turns a plain-language\nrequest into a structured line-item list automatically \u2014 then hands it to\nyou to review before anything is final.<\/p>\n\n
The AI only ever drafts loosely worded line items (what, and how many). This\nplugin resolves each one against your real product catalog and computes\nevery subtotal, tax amount, and total in PHP. The model never sees or sets a\nprice.<\/p>\n\n
This plugin turns a rep's plain-language request into a draft list of line\nitems (description + quantity only \u2014 no prices, no product IDs, no customer\ndata) by calling WordPress's built-in AI Client, which forwards the request\ntext to whichever AI provider the site owner has connected under Settings \u2192\nConnectors. Nothing is sent unless a store rep actively triggers a draft.<\/p>\n\n
This plugin does not choose or hardcode a provider, and ships no API keys \u2014\ncredentials are entered and managed by WordPress core, not this plugin. The\nbuilt-in connectors available in WordPress 7.0 are:<\/p>\n\n
Only whichever provider the site owner has connected is ever called.<\/p>\n\n\n
composer install --no-dev<\/code> in the plugin directory first.<\/li>\n- Upload to
\/wp-content\/plugins\/<\/code> or install via Plugins \u2192 Add New \u2192 Upload. Activate.<\/li>\n- Set your company details under WooCommerce \u2192 Settings \u2192 AI Quotes.<\/li>\n
- Use the AI Quotes menu to draft your first quote.<\/li>\n<\/ol>\n\n\n
\nDoes this replace my existing \"Request a Quote\" plugin?<\/h3><\/dt>\nNo \u2014 it's a different piece of the same workflow. This plugin drafts and\ncalculates a quote document; it doesn't (yet) handle the customer-facing\nrequest form or checkout integration some B2B plugins provide.<\/p><\/dd>\n
Does this send the quote to the customer automatically?<\/h3><\/dt>\nNot in this version \u2014 it generates a PDF for you to download and send\nyourself. Automatic emailing is on the roadmap.<\/p><\/dd>\n
What happens if the AI matches the wrong product?<\/h3><\/dt>\nEvery drafted line is fully editable before you finalize \u2014 fix the\ndescription, price, or swap in the correct product from the search dropdown.<\/p><\/dd>\n
Which AI provider does this use?<\/h3><\/dt>\nWhichever one you've connected under Settings \u2192 Connectors \u2014 this plugin\nhas no AI integration of its own. It calls WordPress's built-in AI Client\n(wp_ai_client_prompt()<\/code>, core since WordPress 7.0), which routes the\nrequest to your connected provider. If no provider is connected, AI\ndrafting is disabled and you can still build a quote manually.<\/p><\/dd>\n\n<\/dl>\n\n\n0.4.5<\/h4>\n\n\n- Change: raised minimum PHP to 8.1 so
sabberworm\/php-css-parser<\/code> can go\nback to its latest release (9.4.0<\/code>, was pinned to 9.0.0<\/code> in 0.4.4) while\nits thecodingmachine\/safe<\/code> dependency resolves to v3.4.0<\/code> instead of the\nold v1.3.3<\/code> \u2014 v3.4.0<\/code> uses explicit nullable-parameter types, so the\nPHP 8.4+ deprecation notices from 0.4.3\/earlier don't come back. Verified:\nzero deprecation notices with full error reporting on.<\/li>\n- Fix: the PDF template's stylesheet is now printed by WordPress core itself\n(
wp_print_styles()<\/code>), not hand-written markup. Every previous shape here \u2014\na literal <style><\/code> block, file_get_contents()<\/code> echoed into one, a <link><\/code>\npointing at a local file path \u2014 kept getting flagged as \"not enqueued\" by\neither the automated check or a human reviewer, even backed by real\n wp_register_style()\/wp_enqueue_style()<\/code> calls. This removes all\nhand-written stylesheet markup from the plugin; dompdf fetches the\nresulting URL the same way it already fetches an optional logo image\n(Options::isRemoteEnabled<\/code>). Verified dompdf correctly fetches and applies\na stylesheet served over HTTP.<\/li>\n<\/ul>\n\n0.4.4<\/h4>\n\n\n- Fix: removed a transitive dependency (
thecodingmachine\/safe<\/code> v1.3.3, pulled\nin by sabberworm\/php-css-parser<\/code>) that emitted PHP 8.4+ \"implicitly\nnullable parameter\" deprecation notices on every request, even though this\nplugin never calls any of its functions \u2014 Composer loads all of a\npackage's files<\/code>-autoloaded code unconditionally. Pinned\n sabberworm\/php-css-parser to 9.0.0<\/code> (the last release before that\ndependency was added) instead of patching around the warnings. No\nfunctional change \u2014 verified the CSS-parsing dompdf relies on for quote\nPDFs still renders identical output, and that loading the plugin no longer\nemits any deprecation notices with full error reporting on.<\/li>\n<\/ul>\n\n0.4.3<\/h4>\n\n\n- Fix: the PDF template's stylesheet is now genuinely registered and\nenqueued with
wp_register_style()<\/code>\/wp_enqueue_style()<\/code> in\n YSQD_PDF::build_html(), not just read from a file. The template outputs\na <link rel=\"stylesheet\"><\/code> for it, which dompdf resolves straight off\nlocal disk via Options::setChroot()<\/code> (no HTTP round-trip, no dependency\non the site's own URL being publicly reachable). Rendered PDF output is\nunchanged \u2014 verified against a real generated quote PDF.<\/li>\n<\/ul>\n\n0.4.2<\/h4>\n\n\n- Fix: \"Tested up to\" bumped to 7.1 (was stale at 7.0, flagged by Plugin Check).<\/li>\n
- No functional changes \u2014 re-confirmed via a fresh Plugin Check run that the\n0.4.1 PDF-template stylesheet fix (see below) still triggers zero\nenqueue-related findings.<\/li>\n<\/ul>\n\n
0.4.1<\/h4>\n\n\n- Fix: the PDF template's stylesheet is no longer written as literal\ntemplate HTML \u2014 it's read from its own file (
assets\/css\/quote-pdf.css<\/code>)\nand echoed in PHP, which WordPress.org's Plugin Check tool now confirms\ntriggers zero enqueue-related findings (the plain <style><\/code> block, and a\n alternative, both did). Behavior and rendered\noutput are unchanged \u2014 verified against a real generated PDF.<\/li>\n<\/ul>\n\n0.4.0<\/h4>\n\n\n- Change: AI drafting now goes through WordPress's built-in AI Client\n(
wp_ai_client_prompt()<\/code>) instead of calling OpenAI\/Anthropic directly.\nThe site owner connects a provider under Settings \u2192 Connectors; this\nplugin no longer stores or asks for an API key. Requires at least<\/code>\nraised to WordPress 7.0 accordingly.<\/li>\n- Fix: quote.php's PDF template markup is a standalone HTML string handed\nto Dompdf, never a WordPress-served page \u2014 clarified in code comments\nafter a review flagged its inline
<style><\/code> block as a missing\nwp_enqueue_style() call.<\/li>\n<\/ul>\n\n0.3.0<\/h4>\n\n\n- Rename: plugin renamed to \"Yuupee Smart Quote Drafting for WooCommerce\" (from\n\"AI Quotes for WooCommerce\") and internal prefix changed
waq_<\/code> -> ysqd_<\/code>\nfor distinctiveness and a 4+ character unique prefix.<\/li>\n- Add: documented third-party AI services (OpenAI, Anthropic) in this readme.<\/li>\n
- Add:
Requires Plugins: woocommerce<\/code> header.<\/li>\n<\/ul>\n\n0.2.0<\/h4>\n\n\n- Add: REST endpoint (
POST \/wp-json\/ysqd\/v1\/quotes<\/code>) exposing the AI-draft\npipeline to external automation \u2014 always creates a draft, never a\nfinalized quote. Authenticated via WordPress core Application Passwords.<\/li>\n<\/ul>\n\n0.1.3<\/h4>\n\n\n- Improve: catalog matching for AI-drafted line items now retries with\nprogressively fewer trailing words when the full description doesn't\nmatch. WordPress's default search requires every word to match somewhere\nin the post, so a single trailing word in a different language than the\ncatalog (e.g. \"Keyboard\" against a French \"Clavier\" listing) could fail\nan otherwise-correct match on brand + model.<\/li>\n<\/ul>\n\n
0.1.2<\/h4>\n\n\n- Fix: the Finalize button's redirect to the PDF download used an\nHTML-escaped nonce URL (from wp_nonce_url()) as a raw redirect target,\ncorrupting quote_id\/_wpnonce and showing \"The link you followed has\nexpired.\" Finalizing now redirects correctly.<\/li>\n
- Fix: a free-text line item's tax used the settings fallback rate even on\na store with WooCommerce taxes disabled entirely, while product-linked\nlines correctly stayed untaxed \u2014 an inconsistency between the two. The\nfallback rate now only applies when the store has tax enabled at all.<\/li>\n<\/ul>\n\n
0.1.1<\/h4>\n\n\n- Fix: every form submission (New Quote, Save Draft, Finalize, Download,\nDelete) failed with a blank HTTP 400 \u2014 handlers were registered on the\nwrong WordPress hook (
admin_action_*<\/code> instead of admin_post_*<\/code>, the\nhook admin-post.php actually dispatches on), so nothing ever ran.<\/li>\n<\/ul>\n\n0.1.0<\/h4>\n\n\n- Initial release (Phase 1): AI-drafted line items, catalog matching,\neditable quote editor, PHP-computed totals, branded PDF export.<\/li>\n<\/ul>","raw_excerpt":"Draft a branded, calculated quote from a plain-language request \u2014 checked against your real catalog, computed by the plugin, never by the AI.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/354061","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=354061"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/abdoudiba"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=354061"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=354061"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=354061"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=354061"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=354061"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=354061"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}