Couponis

A coupon theme judged by its intake, not its homepage

Couponis is a directory theme, and directories live or die on what is in them. The vendor's description starts there too: coupons come from visitors through a front-end submit form, from an affiliate network's XML or CSV file, or from both at once.

Everything else in the theme is arranged around that flow. The page builder shapes how listings look, but the decisions that matter are intake, expiry, moderation and whether a code is worth clicking. If you are picking between coupon themes by scrolling previews, this one is better evaluated by mapping a feed and running a submission through the queue.

Importing affiliate feeds with WP All Import

Imports run through WP All Import rather than a bespoke importer inside the theme folder, and the vendor states the free version is enough. Mapping is drag-and-drop, according to the vendor, and documented in the theme documentation. That makes the plugin's own behaviour — field mapping, scheduling, image handling — part of your build, so read WP All Import's limits alongside the theme's.

The changelog shows this path being maintained: an exclusivity field added to import (1.8), ALT text fields for coupon and store images (1.6), fixes for images kept in WP All Import's files folder (1.7), and importer updates in 3.1.4, 3.1.5 and 3.2.0.

One field deserves attention before you map a feed. Version 3.1.8 added an additional URL per coupon, for cases where a code only applies to a specific product or landing page instead of the store's homepage.

Front-end submissions with a review gate

The submit form lets visitors add coupons, and the vendor says those submissions must be reviewed before publication. That gate is the difference between a directory people trust and one full of codes that expired last spring.

The submit workflow has picked up pieces over time: an email notification on submission and tags on the form (3.2.0), AJAX store and category selection for search and submit (2.8) so a long store list can be typed rather than scrolled, and a setting to disable submit altogether (2.2). An import-only site therefore does not have to display a form it never intends to service.

Three coupon types, including one most directories skip

The vendor defines three types with different visitor actions. Coupon Code is an online code entered at checkout. Online Sale sends the visitor to a sale page. In Store Coupon is a printable coupon taken to a physical shop.

The third type is the one to notice. Printable coupons need a detail page that reads well on paper and on a phone held up at a counter, which is a different design problem from a copy-to-clipboard code box. Version 2.8 added a setting for which coupon types are available, so a site can hide formats it does not publish instead of leaving them in the submit form.

Expiry dates, countdowns and sorting by time

Coupons can run indefinitely or end on a date, and the vendor says both are supported, with expire dates and countdown clocks shown to visitors. Visitors can sort listings by expiry time — useful when the newest entry is not the one still worth using.

Time handling goes finer than a date: version 1.8 added a time setting for expiry and an option to show that time next to the date on coupon boxes. A sale ending at 18:00 is a different offer from one ending at midnight, and the changelog also records an early fix for coupons expiring the day before (1.4) and expired filters in admin listings (2.0) and in the coupon elements (3.1.7).

Voting as both trust signal and maintenance queue

Visitors report whether a code worked, and the vendor says the resulting success rate is shown graphically and numerically. That percentage is the theme's closest thing to a reputation system.

The mechanics extend beyond a badge. Version 3.1.4 added sorting by success rate, 3.1.7 added a vote reset on the coupon edit screen, and 3.1.9 added an admin filter listing coupons below 50% success. That last one turns voting into housekeeping: sort the failures, check the codes, reissue or remove.

The fair caveat is volume. A coupon with no votes has no meaningful percentage, so the badge does little until traffic arrives.

Smart Search that filters out dead codes

The vendor's Smart Search description says only active coupons appear in search listings, and that each user's listing type and sort order are remembered and reapplied on later searches until they change it. Hiding expired codes is a small-sounding rule with a clear effect: search results stay usable.

Version 3.1.9 added a dedicated search box element with store autocomplete — after three typed letters, matching stores appear in a dropdown. On a directory organised by store, suggesting store names beats suggesting coupon titles.

Registered users, saved coupons and the social login caveat

Registered visitors get profile pages where, per the vendor, they can save favourite stores and coupons and track what they have used. That is a retention feature, and it pays off only with repeat traffic.

The vendor also describes social login using Facebook, Twitter and Google+. Google+ has not been a usable login provider for years, and the changelog records Google+ sharing being removed in 3.1.1 while social login moved into the theme — which makes the provider list something to confirm in the current theme options rather than take as fixed. Later releases added account deactivation, registration terms, a hidden captcha and GDPR support (3.1.3, 2.6), a set of features that suggests registrations are handled seriously.

Elementor, WPML and the builder elements

The vendor's description talks about drag-and-drop page building without naming the tool; the changelog settles it at version 3.1.5, which added Elementor support. The marketplace compatibility attributes, observed on 4 November 2026, list Elementor and WPML. Those are vendor and marketplace declarations, not results from running the theme against your plugin stack.

A few elements are written for the coupon workflow rather than general layout: a Store listing element and a Coupons By Tags element (3.1.9, 3.1.8), and link recognition in the Button element for #submit, #account and #logout so a custom header can point at those pages without hunting for URLs.

Translation, demo content and what is not in the package

Translation follows the conventional route: a POT file in the language folder, edited with Poedit, with RTL layouts accounted for in the design according to the vendor.

The ThemeForest file list names PHP, CSS and JS files. The vendor states plainly that demo images are not included and placeholders are used instead to avoid image-licensing problems, so the photography in the preview has to be licensed separately. Demo content imports in one click — the changelog records the switch to a one-click importer in 3.2.0 — and arrives with sample coupons, stores and copy that you replace rather than extend.

The vendor's software list spans WordPress 4.9.x through 7.0.x. That is a statement of what the vendor reports the theme runs on, not a measurement of how it behaves with your caching, child theme or plugin mix.

Questions & answers