| 开发者 | emberprice |
|---|---|
| 更新时间 | 2026年7月30日 06:42 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
.99/.90 endings, or nearest multiple), existing sale-price policy, and per-category overrides.$ 1.234,56, codes with leading zeros or no code column at all, section rows, discontinued items. EmberPrice's column detection and matching cascade are built around exactly these cases, and nothing is ever written to a product until you've seen the diff.
Safety by design
No. Nothing is written to any product until you reach the last step and explicitly apply the job. Every earlier step (mapping, matching, rules, preview) is read-only.
XLSX, XLS, and CSV. PDF price lists (text-layer only, not scanned images) are planned for a future update.
Yes. The matching cascade doesn't require a SKU: it also matches by learned alias (from your past confirmations), exact product name, and fuzzy name matching, so lists with only a description column still resolve.
No. This release doesn't use one at all: the full wizard runs on local column detection and matching (alias, SKU/GTIN, exact name, fuzzy). AI-assisted matching and mapping is planned as a future opt-in, bring-your-own-key (BYOK) Pro feature; this plugin doesn't have or need its own AI backend.
Nothing today: this release doesn't include the AI-assisted matching code at all, so it never connects to Anthropic, OpenAI, or any other external service. When the feature ships in a future update, it will only run while explicitly enabled with your own API key, sending the supplier's own row text (names/codes) and matching candidates already in your store's catalog (product names, SKUs) only. Never customer, order, or other personal data.
Yes. The matching cascade resolves a supplier row directly to a variation (by its own SKU, name, or fuzzy match), and pricing rules apply to the matched variation.
Any row the cascade isn't confident about is left for manual review: nothing auto-applies without a confirmed match. You can always search and manually assign a row to any product.
Yes. Every apply snapshots the previous prices first. Roll back any applied job from the History screen, not just the most recent one: snapshots are kept until the retention period expires.
Not in this version: EmberPrice is scoped to regular/sale price updates from a supplier list. Stock, cost fields, multi-currency, and scheduled/watched-folder imports are on the roadmap but not implemented yet.