Updates for lifetime, unlimited sites, unlimited downloads, and regular updates.
$3.99
Docket is a WooCommerce plugin published on CodeCanyon by the author wpweb, and its title places it in the group of collections, wishlist and watchlist tools. Its listing describes a way for customers to gather and share products they like, want or recommend. It presents the plugin as a means of organising favourite products and showing buyers what a store has available to share. This entry summarises what the listing sets out, along with the practical questions a store should answer before adopting the plugin.
The listing states that the plugin lets customers gather and share products they like, want or recommend. It also says the plugin can be used to show buyers what a store has for sale or share, and to help people organise their favourite products into groups. Those are the core purposes set out on the listing, and sharing is one of the main themes it emphasises.
The product title groups the plugin under collections, wishlist and watchlist. A wishlist is commonly understood as a list a shopper keeps for later, and a watchlist as a list of items a shopper wants to keep an eye on. Those terms describe the category the plugin sits in. The listing itself does not walk through how a shopper creates a list or adds an item to one, so a prospective buyer should look at the linked documentation or demonstration for those steps.
The most specific integration described on the listing is with Follow My Blog Post, a separate CodeCanyon item. The listing states that the Collections extension is fully integrated with Follow My Blog Post, and that email alerts for new items in a followed collection can be enabled automatically through that integration. A shopper who follows a collection can therefore be notified when something new is added to it, provided the integration is set up.
Because the alerts depend on a second product, a store that wants this feature should install both items and confirm that they are compatible with the same WordPress and WooCommerce versions. The listing does not describe the setup steps for the integration, and it does not cover the content or timing of the emails, so the documentation or a test alert is the best way to see how the feature behaves in practice.
Docket suits WooCommerce store owners who want shoppers to gather products into lists and to share those lists with others. The listing’s wording points to several natural uses, such as keeping track of items a customer intends to buy later, passing a set of recommendations to friends or family, and presenting a curated group of products to a visitor. Each of these uses rests on the gather-and-share function that the listing describes.
Stores with a broad catalogue may find groups of products easier to manage when they can be arranged into themed collections, such as a seasonal range, a set of gift ideas or a group of accessories for one product line. Stores with a narrow range may get less value from the feature, because fewer items are likely to be gathered in the first place. This is a general observation about product lists rather than a claim about how the plugin performs.
The listing states that the plugin is compatible with WordPress 6.3 to 6.7 and WooCommerce 6.x to 9.x. Its most recent changelog entry, for version 1.7.1 and dated 18 July 2024, says the plugin was tested with WordPress 6.6 and WooCommerce 9.1.2. Because those figures come from 2024, a store running newer releases should test the plugin on a staging copy before it goes live.
The listing also describes the plugin as optimised for the Gutenberg editor, and it names major browsers, including Firefox, Safari, Chrome and Edge, among those it supports. It does not give PHP or server requirements. Those should be checked against the hosting environment before installation, because a mismatch can stop a plugin from working even when the WordPress and WooCommerce versions are correct.
The listing links to documentation and to a live demonstration. Those resources are the most direct route to understanding how collections are created, how items are added to and shared from a list, and how the Follow My Blog Post connection is configured. Reading them before installation saves time, because it shows whether the workflow suits the store’s customers. When reading documentation, note the versions it refers to, since older guides may describe screens or steps that have changed.
The listing also includes a changelog. A changelog is useful for tracking what has changed between releases, for spotting fixes that matter to a particular store, and for checking when the plugin was last updated. A reader who sees that the most recent entry dates from 2024 may want to look for newer updates before relying on the plugin.
A sensible first step is to install the plugin on a test copy of the store and read the documentation. Create a small number of test products, then move through the shopper journey from browsing to sharing. Check how the lists look on desktop and mobile screens, and confirm that shared content behaves as expected for someone who is not logged in. If the Follow My Blog Post integration will be used, send a test alert from start to finish so that its timing and content can be judged.
Shared lists can reveal what a person is interested in, so a store that offers sharing should consider how that information is presented and who can see it. Review the store’s privacy notice to make sure it covers shared lists, and explain to customers in plain language what happens when they share a list or follow one. Clear wording near any sharing option helps shoppers understand what will be visible to the people they share with. Keeping these points clear builds trust and reduces questions later.
A plugin that depends on WooCommerce and on a second plugin needs regular attention. Keep WordPress, WooCommerce and both plugins updated, review each changelog before applying an update, and retest the key journeys after any major release. Keep a copy of the settings so that the configuration can be restored if an update causes a problem. Where alert emails are used, a simple periodic check that they still arrive helps confirm that the connection is working.
Whichever tool a store uses to group products, clear names help shoppers understand what a list contains. Names that describe a purpose, such as a gift idea list or a set of items for a particular room, tend to be more useful than generic labels. A short description sets expectations, and an accurate description serves shoppers better than a clever one. Periodic reviews of names and descriptions help keep a store’s lists easy to navigate as the range changes over time.
Store owners who want to know whether shared lists support sales can compare visits, product views and orders for items that appear in lists against items that do not. Simple spreadsheets or standard analytics reports are often enough to show a trend. Measures such as repeat visits, the number of shared links opened from outside the store, and changes in average order size give a broader picture than a single count. The listing does not describe built-in reporting, so store owners should confirm what data is available before setting any targets.
Several mistakes appear often when a store introduces list features. Launching without clear wording leaves shoppers unsure what a list is for. Testing only while logged in can hide problems that other visitors would notice, so shared links should also be opened in a private browser window. Ignoring mobile layouts is another frequent error, because lists are often viewed on phones. Finally, updating the plugin without reading the changelog can change how existing lists behave, and that change may only be noticed after customers report it.
Docket is a WooCommerce collections, wishlist and watchlist plugin that its listing presents as a way for customers to gather and share products, with an email alert connection to Follow My Blog Post that can be enabled. The listing is clear on those points and links to documentation and a demonstration. The areas that need checking before a live launch are how collections are created, how the integration is configured, and whether the tested versions match the store’s current releases.