Pin Magic – Pin Creator for Pinterest

Manually creating Pinterest pins eats your time. Every new blog post means opening Canva, dragging an image in, writing a hook, and exporting — then doing it again next week. For food bloggers who live and die by Pinterest traffic, the loop never ends.

Pin Magic collapses the design step into one click, inside WordPress. Pick a blog post, choose a template, and Pin Magic writes a suggested title, builds the 1000×1500 pin image from your own photo, and hands you the finished file — downloaded to your computer and saved to your Media Library.

Key features

• One-click pin design — turn any blog post into a Pinterest-ready pin image without leaving WordPress.
• 5 templates designed for food photography — Bold Banner, Simple, Earthy Kitchen, Neon Pop and Split Diagonal (the pin builder renders all five in your browser; if your browser cannot run the designer, pins fall back to a server-rendered version).
• Color, alignment and image controls — match pin accents to your brand, choose left/center/right alignment, and swap in any image from your media library.
• Download or keep in Media — every finished pin is saved to your Media Library and can be downloaded with one click.
• Mark as pinned — tick a pin once you have posted it so your dashboard shows what is done.

Pin Magic Pro

Pin Magic designs the pin. Pin Magic Pro posts it. Pro is a separate plugin, available from https://pinmagic.tech/pro, that replaces this one and adds:

• Connect your Pinterest account and publish pins straight from the dashboard
• Schedule pins and manage them on a calendar
• The full template library (15 designs)
• A Pinterest analytics dashboard
• Pin copy written for you with no monthly allowance

This free plugin shows the ten Pro templates as preview images on the Templates screen and in the pin builder, so you can see the rest of the library. Their designs are not included in this plugin.

The one thing that runs on our servers

Writing the pin title and description is the one job Pin Magic does not do on your site. It runs on Pin Magic’s own servers, which send your post details to Google’s Gemini language model and return a suggested title and description. Because it costs us money per request, it carries a monthly allowance of 20 pin titles. You can always write or edit pin copy yourself, with no limit, and building the pin never depends on it.

Privacy and transparency

Pin Magic is honest about what leaves your site. When you ask for a pin title, Pin Magic sends the post title — plus the featured image’s alt text, the titles of pins you already made for that post, and recipe details if you use a recipe plugin — to its pin-copy service (a Cloudflare Worker that proxies to Google’s Gemini API). Nothing else leaves your site: the pin image is rendered in your browser and saved on your own server. Pin Magic adds no tracking pixels and no cross-site tracking. See the External services and Privacy sections below for the full breakdown.

Bundled third-party libraries

These open-source libraries ship inside the plugin as minified files so nothing is ever loaded from a remote server. Each carries its upstream licence file in the plugin, and its full unminified source is available at the link below.

• html2canvas 1.4.1 (MIT) — renders a pin design to an image in your browser, so pin images are produced on your own machine rather than on a server. Source: https://github.com/niklasvh/html2canvas — licence: assets/vendor/html2canvas/LICENSE.txt
• Google Fonts (SIL Open Font License 1.1) — Inter, Lora, Montserrat, Oswald and Space Grotesk, used by the pin templates. Only the subsets the included templates need are bundled, so rendering a pin never requests a font from a remote server. Source: https://github.com/google/fonts — licence and per-family copyright: assets/fonts/google/OFL.txt
• Poppins (SIL Open Font License 1.1) — used by the server-side pin renderer. Source: https://github.com/itfoundry/Poppins — licence: assets/fonts/OFL.txt

Bundled photography

The example food photographs in templates/<name>/sample.jpg exist only to show what each included pin template looks like, on the Templates screen and in the pin builder. The thumb.jpg images in the other template folders are rendered previews of the Pin Magic Pro designs, shown so you can see the rest of the library. None of them are used in any pin you make — your pins use your own images.

Each one is either the plugin author’s own photograph or was obtained from a royalty-free stock library whose terms permit redistribution. All of them are redistributed as part of this plugin under its GPLv3 licence. They are served from inside the plugin and are never fetched from a remote host.

External services

Pin Magic relies on one external service. It is contacted only as described below. Activating the plugin contacts nothing.

Two identifiers are used. The site identifier is a SHA-256 hash of your site URL plus admin email — non-reversible, and neither value is ever transmitted. The install identifier is a random UUID generated on first run and stored in your database; it identifies this installation to the service so one site’s allowance is kept separate from another’s. It contains no information about you or your site, and both are deleted when you delete the plugin.

Pin Magic API (api.pinmagic.tech)
This is Pin Magic’s own service, hosted on Cloudflare Workers. It performs the following functions, none of which can be done locally inside the plugin:

1. Pin copy creation. When you ask for a pin title or description, the plugin sends the post title, recipe data if a recipe plugin is present, the alt text of the featured image, the titles of pins you have already made for that post (so new copy does not repeat them), the site and install identifiers, and your current plan (“free” or “pro”). The service uses Google’s Gemini language-model API to compose the text and returns it. This runs only when you request it.
2. Allowance check. While the pin builder is open, the plugin asks this service how much of your monthly pin-copy allowance remains, so the counter on screen is accurate before you spend any of it. It sends the site and install identifiers and your current plan, and no post content. Nothing is consumed by asking.
3. Plan configuration. Once a day the plugin fetches the current allowance figures (no identifying data). The values are the same ones built into the plugin.

No author name, email address, or IP address is sent to this service. Terms of Service: https://pinmagic.tech/terms — Privacy Policy: https://pinmagic.tech/privacy. Subprocessors: Cloudflare, Inc. (https://www.cloudflare.com/privacypolicy/) and, for pin copy generation only, Google LLC (https://policies.google.com/privacy).

The “Upgrade” links in the plugin open https://pinmagic.tech/pro in a new browser tab. No checkout or payment form is embedded in the plugin, and nothing is sent when you follow the link.

Privacy

Pin Magic uses one third-party service, which receives data only when you actively use the corresponding feature.

Pin copy creation
When you create a pin title or description from a blog post, Pin Magic sends the following to its pin-copy service (hosted on Cloudflare Workers, which proxies to Google’s Gemini API):

• Post title
• The alt text of the post’s featured image, if it has one
• Recipe details (name, summary, ingredients, total time, servings) — only if you use a supported recipe plugin on that post
• The titles of pins you have already made for that post, so new copy does not repeat them
• A hashed, non-reversible site identifier — a SHA-256 hash of your site URL plus admin email, used only to count your monthly pin creations against your plan’s allowance. Only the hash is sent; your URL and email are never transmitted, and the hash cannot be reversed to recover them.
• An install identifier — a random UUID generated on first run and stored in your database. It carries no information about you or your site; it exists so the service can keep one installation’s cached analytics and allowance separate from another’s. It is deleted when you delete the plugin.
• Your current plan (“free” or “pro”)

No author name, email, IP address, or personal identifiers are transmitted. Neither Cloudflare nor Google retains your prompt content beyond the time required to generate a response. The data subprocessors are Cloudflare, Inc. (cloudflare.com) and Google LLC (cloud.google.com).

Data stored on your site
Pin Magic stores pin history (titles, descriptions, status, error messages) and an error log in custom WordPress database tables on your own site, and keeps each post’s pins alongside that post. All of it lives entirely on your own server, and all of it is removed when you delete (not just deactivate) the plugin. The pin images Pin Magic has built are left in your uploads folder, as deleting a plugin should not remove images you may still be using.

What Pin Magic does not collect
Pin Magic itself includes no advertising or cross-site tracking pixels and does not sell your data. The pin-copy service counts how many pins you create each month against your plan’s allowance, keyed to the hashed, non-reversible site identifier described above (which is stable across reinstalling the plugin), but stores no personal information.

1. In your WordPress admin, go to Plugins → Add New, search for “Pin Magic,” click Install Now, then Activate.
2. Click Pin Magic in the admin sidebar, pick a blog post and click Create pin.
3. Choose a template, review the copy, and on the last step download your pin or find it in your Media Library.

That’s the whole setup. No accounts, no API keys.

Does this plugin post to Pinterest?

No. Pin Magic is the designer: it makes the pin image. Posting, scheduling and the calendar are in Pin Magic Pro, a separate plugin from https://pinmagic.tech/pro. Install Pro and it takes over from this plugin; every pin, template choice and setting you made here carries over.

Why don’t some of my posts show in the Pin Magic grid?

Pin Magic builds a pin out of one of your own images, so a post needs either a featured image or an image from your media library in its content. Posts with neither can’t produce a pin, so the grid leaves them out rather than offering a button that can only fail. The count of what’s hidden, and the reason, is shown above the grid. To list every post instead, add add_filter( 'pinmagic_hide_imageless_posts', '__return_false' ); to your theme’s functions.php.

Why are some templates marked “Pro”?

Those ten designs are part of Pin Magic Pro. This plugin includes a preview image of each so you can see the full library; the designs themselves — their stylesheets and fonts — are not in this plugin. Clicking one explains how to get Pro.

How does pin copy creation work?

Pin Magic sends your post title, the featured image’s alt text, the titles of any pins you already made for that post, and recipe details if a recipe plugin is present, to its pin-copy service — a Cloudflare Worker that proxies to Google’s Gemini model. The service returns Pinterest-optimized title and description suggestions you can edit. You never see or manage an API key, and no personal data leaves your site.

What happens when the monthly copy allowance runs out?

Nothing stops. The pin builder opens with the copy fields blank and you type your own title and description. The allowance resets on the first of each month. Pin Magic Pro has no allowance.

Can I use my own images instead of my blog post’s featured image?

Yes. Every pin has a Change image button — swap in any image from your media library, or upload a new one straight from your computer. You can also upload a pin you designed elsewhere and use Pin Magic to write its copy.

Where do my finished pins go?

Every pin is saved to your Media Library (under the post it was made for) and offered for download on the last step of the builder. The files live in your uploads folder like any other image.

Will my pins lose data if I uninstall?

Deleting the plugin removes its database tables (pin history, error log) and the pin data stored against each post, unless Pin Magic Pro is still installed: the two plugins share that data, so it is only removed when the last of them is deleted. Deactivating without deleting keeps everything intact. Pin images already built are left in your uploads folder.

3.0.2 — 2026-10-23

• Each plugin now ships its own uninstall.php, so deleting one never loads the other, in any order, including bulk deletes.
• Sites that ran Pin Magic before the 3.0 split now see a one-time notice explaining what moved to Pin Magic Pro, with a one-click email to claim the free Pro licence.
• Clearer wording throughout: Pro templates are shown with a star, never a padlock, and the monthly allowance message says exactly what it covers (written copy only; building pins never stops).
• Pin Magic Pro: a lapsed trial or licence now points to the Account screen and reminds you the free plugin keeps designing.

3.0.1 — 2026-10-23

• Deleting the free Pin Magic plugin after installing Pin Magic Pro (or the other way round) no longer removes your pins, settings or Pinterest connection. The two plugins share that data, and it is only removed when the last of them is deleted.

3.0.0 — 2026-10-23

Pin Magic is now two plugins, and this one is the designer.

To comply with the WordPress.org plugin directory’s rules, the publishing half of Pin Magic has moved into a separate plugin, Pin Magic Pro, available from https://pinmagic.tech/pro. The directory does not allow a free plugin to carry code that only works after a purchase, and the only honest way to offer publishing as a paid feature is to ship it separately. We chose that over dropping the free plugin.

What this plugin does now:

• Designs pins from your blog posts, exactly as before: pick a post, pick a template, review the copy with a live preview, and the last step hands you the finished pin — downloaded, and saved to your Media Library.
• Includes five templates: Bold Banner, Simple, Earthy Kitchen, Neon Pop and Split Diagonal. The other ten appear as previews and are part of Pro.
• Lets you tick a pin as “pinned” once you have posted it, so the dashboard shows what is done.

What moved to Pin Magic Pro:

• Connecting to Pinterest, publishing, scheduling, the Calendar tab and the Analytics page.
• The ten templates: Cookbook, Spotlight Arch, Statement, Elegant Frame, Magazine Cover, Notebook Grid, Placecard, Classic Dark, Minimal Light and Recipe Card.

Early installer? We split our designer and publisher to comply with WP directory rules. If you downloaded before 2026-10-23, email support@pinmagic.tech from the address on your WordPress site and we will send you a free Pin Magic Pro licence. Nothing you made is lost: pins, settings and the Pinterest connection stay in your database, and Pro picks them up when you install it.

Also in this release:

• The minimum WordPress version is 6.2 (it was 6.5); the scheduling library that set the higher floor is no longer in this plugin.
• Every finished pin is now registered in the Media Library, not only saved to the uploads folder.
• Removed the Pinterest connection and publishing settings, the Calendar and Analytics screens, and the libraries that served them (FullCalendar, flatpickr, Action Scheduler).

2.11.46 — 2026-10-21

• The Recipe Card template’s ruled lines now appear on published pins. The lines rendered in the gallery and the wizard preview but were dropped from the finished image by the in-browser renderer, so every Recipe Card pin went out without them. Same look, now baked into the PNG.

2.11.45 — 2026-10-19

• Activating the plugin no longer contacts any server. It used to fetch its plan configuration from Pin Magic’s service the moment you activated it, before you had agreed to anything. That fetch now happens only on the daily background refresh, which is scheduled when you first open WordPress admin. The values it fetches are the same ones built into the plugin, so nothing looks different.
• Clarified in this readme that activation itself contacts nothing.

2.11.44 — 2026-10-19

• Fixed: scheduling a pin for later the same day was silently dropped on sites west of UTC. The chosen time was compared against the clock in the wrong time zone, so on US Pacific a pin set for 5pm while it was 11am looked like it was in the past — it was skipped, and the message blamed the time you picked. The window was as wide as your time zone’s offset.
• Fixed: a pin whose publish could not be confirmed offered only “Re-publish anyway” on the Pin Schedule tab. The warning note and the “Mark as published” button — the option that resolves it without risking a duplicate on Pinterest — were missing from that screen.
• Fixed: “Try Again” after a scheduling failure did nothing at all.
• Fixed: going back from the scheduling step could leave the builder on a spinner indefinitely if the request failed.
• Fixed: a connection that was healthy could be marked expired when two pins published at the same moment near the monthly token renewal, which then blocked creating or publishing until you reconnected by hand.
• Fixed: a brief outage of our own service while publishing could mark your Pinterest connection expired even though nothing was wrong with it.
• Fixed: disconnecting Pinterest now also clears the selected board, so connecting a different account no longer tries to publish to the previous account’s board.
• Fixed: the server-side renderer stamped a small “P” mark on pins. It was removed from the other two renderers some time ago and should have gone from this one at the same time.
• Fixed: the check for a stuck WordPress cron never ran, and the “last published” time and overdue warning in the diagnostic were off by your time zone’s offset.
• Deleting the plugin now also removes the pins stored against each post, not just the history tables. Pin images already built are left in your uploads folder.
• Fixed: the Pinterest status badge in the dashboard header never appeared.
• Corrected the readme where it overstated what a change had done, what is sent for per-pin analytics, and which database queries use placeholders.

2.11.43 — 2026-10-17

• Fixed: the message shown when Pinterest refuses a pin for lack of production access displayed two stray backslashes.

2.11.42 — 2026-10-15

• Added a section describing the example photographs bundled with the plugin and what they are used for.

2.11.41 — 2026-10-15

• Running out of the monthly pin-copy allowance can no longer stop a pin being built, even if the service answers oddly. The previous release keyed that on the reason text the service sends back; a rate-limit response that arrived without one could still halt the build. The HTTP status is now what decides, so this no longer depends on wording.
• When the allowance is spent, the pin builder now says so above the copy fields instead of just presenting them empty.
• The Analytics page now explains every situation in plain words — not connected, connection expired, Pinterest access pending, or the service not responding. Previously only the first two did, and a service outage was shown as a sample dashboard whose caption said your pins were still gathering data.
• The ten error messages stored against a post and shown in the post editor are now translatable; only their counterparts elsewhere were.
• Removed a leftover flag and six comments describing a “first pin free” allowance that the plugin does not actually implement — creating a pin has always required Pinterest to be connected, so that nothing is built that cannot then be published.
• Corrected the readme’s description of what is sent for pin copy: it listed the post URL and a content summary, neither of which is sent. The Privacy section already had this right; the other three places now agree with it.
• Corrected three more code comments that described their own code inaccurately, and restored the indentation of one file that a tidy-up pass had flattened.

2.11.40 — 2026-10-15

• Fixed: running out of the monthly pin-copy allowance stopped you building a pin at all, on three of the four ways to start one. Designing and rendering a pin happens entirely on your own site and has never been limited. The pin wizard already handled an exhausted allowance by opening with the copy fields blank so you could type your own words; the Generate Pins button in the post editor, the dashboard’s Generate action and Retry did not — they stopped with “Please try again”, which could not succeed until the following month. All four now behave the same way.
• Fixed: when the pin-copy service failed for any reason, the real reason was discarded and replaced with a generic “please try again”, so nothing useful reached the error log. The actual cause is now recorded.
• Fixed: the Pin Schedule tab showed English text on translated sites. The calendar’s translations and its status labels were only attached to a second, unlinked copy of the calendar screen, so the tab everyone actually uses fell back to English and showed a pin awaiting checking as “Needs verify” rather than “Needs checking”. Both now share one set of text.
• Every error message the plugin can show you now goes through WordPress’s translation functions. Forty-two of them — mostly Pinterest and pin-copy service errors — were still fixed English.
• The Analytics page now says plainly that Pinterest isn’t connected yet, instead of showing a sample dashboard with example figures.
• Fixed: the pin wizard could sit on “Rendering pin images” indefinitely if your login expired mid-upload, instead of reporting the failure.
• Fixed: a dropped connection while uploading a custom pin image reported “Network error (HTTP ?)” instead of explaining that the server could not be reached.
• The pin-count totals in the post editor now read “1 pin generated” rather than “1 pin(s) generated”, and the Analytics chart tooltip is translatable.
• Readme corrections: it listed a logo-upload feature the plugin no longer has, described the pin-copy payload inaccurately in the Privacy section, overstated how often the analytics figures are fetched, and pointed you at a diagnostics panel only visible in debug mode. It now also documents the link tagging added to published pins, and lists every bundled font and library with its licence and source.
• Removed code that nothing used: an unused Pinterest token endpoint, an unused page-list constant, an unreachable database call, and 3.4 MB of unreferenced preview images.
• When the server-side renderer is asked for a template it has no design for, it now records which design it used instead of substituting one silently.

2.11.39 — 2026-10-14

• Removed an unused reference to Pinterest’s sandbox API server. Connecting to Pinterest has been sign-in-only for some time, and a sign-in always produces a live-account connection, so the sandbox setting could no longer be reached. The address has been taken out of the code rather than left sitting unused.
• Added a “Bundled third-party libraries” section to this readme listing every included library, its version, its licence, and a link to its full source code.
• Tidied the notes that explain why a handful of database and image-loading calls are written the way they are, so each one states its reason on the spot.

2.11.38 — 2026-10-13

• Pin Magic is now fully translatable. Every piece of text the plugin shows you — pages, buttons, confirmations, progress messages and error messages, including the ones that appear in the pin builder and the calendar — now goes through WordPress’s translation functions, so the plugin can be translated into any language. Previously much of it was fixed English that no translation could reach.
• Fixed: a pin that may already have published could be published twice. When Pinterest returned a server error, Pin Magic decided whether the pin had gone out by reading the wording of Pinterest’s reply. Pinterest usually sends its own wording, so that check missed, and the pin was filed as a clean failure with a Retry button — which could post a second copy of a pin that had in fact published. Pin Magic now reads the HTTP status itself, and such a pin is held for you to check rather than retried.
• Fixed: pins waiting on a Pinterest reconnection would not resume on a translated site. After you reconnected Pinterest, Pin Magic found the pins to resume by searching their error text for English phrases. On a site in any other language nothing matched and the pins stayed stuck. Each pin now records a language-independent reason code, and resuming keys off that. Pins stranded by an older version are still picked up.
• Counts now read correctly: “1 pin scheduled” rather than “1 pin(s) scheduled”.
• The date your monthly pin-copy allowance resets is now formatted in your site’s language.
• A pin held for checking now reads “Needs checking” instead of “Needs_verify”.
• A pin’s status, the reason a publish failed, and the date and time shown in the calendar all now follow your site’s language and date settings.

2.11.36 — 2026-10-12

• The post grid now lists only posts Pin Magic can actually make a pin from — a post with no featured image and no image in its content can’t produce one, so offering a “Create pin” button on it only led to an error. The number left out, and why, is shown above the grid.
• Admin notices from WordPress and from other plugins now render in their own block above the tabs on the Pin Magic pages, instead of being injected into the middle of the page heading and pushing the controls out of line. Pin Magic does not hide other plugins’ notices.
• The Create pin / Upload pin buttons line up across the grid regardless of how long a post title is.
• Fixed: a post whose only image is in its content (no featured image) showed an empty grey card in the grid instead of that image.
• Removed the optional Cloudflare Turnstile anti-spam check from the support form. It loaded a script from an external host, and it was never active for anyone — it only ran if a key was configured in wp-config.php. The form’s existing protections (nonce, hidden honeypot field, and a 3-per-hour rate limit, on a page only logged-in editors can reach) are unchanged.
• Fixed: on a site served over HTTP, the notice explaining that Pinterest requires HTTPS was rendered as a third column beside the heading and button, squashing the layout. It now sits on its own line.
• Security: a request that schedules several pins at once checked that you could edit the post, but not that each pin belonged to it. On a multi-author site a Contributor could have rescheduled or cancelled another author’s pins. Every pin is now checked individually, the same way the other scheduling requests already did.
• Building a pin no longer stops when the month’s allowance of automatically written copy is used up. The pin builder is on your own site and has never been limited; it now opens with the fields blank so you can type your own words, which is what the message always said you could do.
• Updated the bundled Action Scheduler library to 3.9.3, and moved it into the standard vendor/ directory.
• Added the upstream licence files for the bundled FullCalendar, flatpickr, html2canvas and font assets.
• Removed 24 unused image files, including several carrying the plugin’s former name.
• The plugin’s own table names now go through prepare()’s identifier placeholder instead of being written into the query by hand. (WordPress’s own table names, such as the posts table, are still referenced through WordPress properties, which is the standard way and never involves anything you typed.)
• Documented the allowance check the pin wizard makes, the install identifier the service uses to keep sites’ cached data apart, and board creation — and corrected the analytics cache window and the pin-copy payload description.
• Documented every call the plugin makes to Pinterest — board lists and the daily connection check, not just publishing — and the Pinterest analytics request under External services — the Analytics page asks Pin Magic’s service for your Pinterest figures, and that was not previously disclosed.
• Queries against the plugin’s own tables now bind the table name through prepare()’s %i placeholder.
• The post-grid filter can be switched off with a filter — see the FAQ.

2.11.22 — 2026-09-13

• Scheduling now works everywhere. Pin Magic scheduled pins through a library called Action Scheduler but did not include it, so on any site that did not also run WooCommerce, scheduling simply returned an error. The library now ships with the plugin. If scheduling never worked for you, this is why.
• Every feature that runs on your site is now unlimited for everyone. Custom image uploads, publishing to Pinterest, and how many pins you can queue at once previously carried monthly limits. They no longer do, and the code that enforced them has been removed.
• The only remaining allowance is on pin copy written for you automatically, because that runs on Pin Magic’s servers and calls a paid language-model API. Writing your own copy is unlimited.
• Fixed: two places still quoted monthly figures that no longer exist, which would have printed a raw placeholder on screen.
• Minimum WordPress is now 6.5, required by the bundled scheduling library.

2.11.21 — 2026-08-04

• Security: Pin Magic’s editing screens are available to Contributors and Authors, but its behind-the-scenes requests only checked that you could edit posts in general — not that you could edit the post you asked about. On a multi-author blog that meant one author could read or change another author’s pin titles, descriptions and schedules, or publish their pins. Every one of those requests now checks permission for the specific post, using the same rule WordPress applies in the editor. Single-author sites were never affected.
• Hardened the same requests against malformed data, which could previously end a request with a PHP error instead of a clean message.

2.11.20 — 2026-08-04

• Fixed: connecting your Pinterest account sent a malformed return address to Pinterest. The connection worked anyway, but it was wrong and is now correct.
• Fixed: rendering a pin ran four calls that PHP 8.5 has retired, printing deprecation notices into the log on sites with debugging switched on.
• Failed pin-copy attempts now appear in the plugin’s own error log — where the dashboard health widget can show them — instead of only in the server’s PHP log.
• Corrected the template count throughout this readme: there are 15, not 16.
• Removed an old stylesheet that hadn’t been used in months and was still being included in the download.
• No change to how anything works or looks.

Earlier versions

Entries before 2.11.21 are omitted. They described a different product: until 2.11.22 the plugin applied monthly limits to things it does on your own server, and earlier builds embedded a checkout. Both are gone — every feature that runs on your site is now unlimited for everyone, and the Upgrade page links out rather than embedding payment. Keeping those old entries would mean shipping present-tense descriptions of behaviour the plugin no longer has.