WPC Order Barcodes - WordPress Plugin

How to Configure WPC Order Barcodes for WooCommerce Orders

WPC Order Barcodes is not just about adding a nice-looking QR code to an order. In this guide, you'll see how to turn it into a practical tool for warehouse workflows, order pickup, ticket validation, packing, and fast order lookup inside the WooCommerce admin. We will go from site preparation to a real-world scenario: create a test order, place the code where it needs to appear, scan it, and confirm that it actually helps your team instead of adding one more unnecessary element to customer emails.

The WPClever product page confirms the core features: automatic generation of a unique barcode or QR code for each order, multiple code types, display in emails and on order pages, a built-in scanner, and the [wpcob_barcode] and [wpcob_scanner] shortcodes. These features are only useful when you decide in advance where the code will be used: in the warehouse, at a pickup counter, at an event, in the customer account area, or on an internal staff page.

This article does not repeat the plugin's short product description. The practical logic matters more here: which settings to check after installation, which code type to choose, how to avoid breaking WooCommerce emails, where to place the scanner, how to troubleshoot camera access, order statuses, and caching, and which alternatives to consider if you need more than an order barcode, such as a full ticketing system or a general-purpose QR code generator.

What Problem the Plugin Solves and Where It Is Actually Useful

WooCommerce already has order numbers, statuses, an orders table, search, emails, and an order view page in the customer account. So WPC Order Barcodes only makes sense if you use it to speed up a specific physical or operational process, not just to generate a code for the sake of having one. If an order needs to be matched quickly to a person, package, box, ticket, pass, reservation, or pickup at the counter, a scannable code saves time and reduces manual errors.

The simplest use case is a warehouse or pickup location. A staff member gets a printout, packing slip, email, or order page with the code. Instead of manually searching for the order number in the WooCommerce orders table, they scan the code and open the order data through the built-in scanner. A second use case is events, reservations, and services where the order effectively acts as an access pass. A third is internal control: a manager checks that the correct order was found, the status was updated properly, and the code is not exposing unnecessary data to the customer.

The plugin delivers the most value when an order moves beyond a purely digital process and becomes a physical action: packing, pickup, attendee check-in, item verification, shift handoff, or status control. If your store sells only digital files and your staff never scans orders, the code may just be extra clutter. In that case, the standard WooCommerce order page and automated emails are probably enough.

What the Sources Confirm

The official WPClever page describes several important capabilities: codes are created automatically for new orders, QR Code, EAN-13, Code 128, Data Matrix, and Code 39 are available, you can use prefixes, change the code type and display positions, show the code in emails, on the Order received page, and in the customer View Order section, and output both the code and the scanner with shortcodes. WooCommerce documentation separately confirms that orders have statuses, are visible to administrators and store managers, and that test orders are useful for checking integrations.

These facts define the scope of this guide. We can confidently explain how to work with orders, statuses, emails, the order page, and shortcodes. But we should not claim that the plugin supports specific hooks, REST endpoints, PDF plugins, third-party POS systems, or automatic status changes after scanning unless those features are explicitly confirmed in sources for WPC Order Barcodes. Those integrations are best verified on a staging site and documented based on actual results.

When a Code Works Better Than an Order Number

An order number is convenient for someone sitting at a keyboard. A barcode or QR code is more convenient when a staff member is holding a scanner, phone, tablet, or laptop camera. In real operations, those are very different situations. In a busy warehouse, manually entering order numbers increases the risk of mistyping a digit, opening the wrong order, or wasting extra time searching. A code turns that into a single action: point the camera, get the result, verify the details.

For a QR code, size and contrast matter. For a linear barcode, width, print quality, and scanner compatibility matter. That is why your code type choice should not be abstract. It should match the actual place where the code will be used. If staff will scan it with a phone camera directly from the order page, QR Code is usually the easiest option. If you use a warehouse handheld scanner that expects linear formats, Code 128 or Code 39 is worth testing first. If the code will appear in an email and may be printed by the customer, make sure the email template does not compress the image until it becomes unreadable.

Who WPC Order Barcodes Is For and When Another Approach Makes More Sense

The plugin is especially useful for WooCommerce store owners who already know exactly what they plan to scan. That might be a small store with local pickup, a warehouse, a training business with paid classes, an event organizer, a service center, a showroom, a workshop, or any team that processes orders manually. In projects like these, a scannable code becomes the bridge between WooCommerce and a physical action.

A strong sign that the plugin fits your workflow is when your team already repeats phrases like "find the order by number," "check whether the customer paid," "mark it as picked up," "match the box to the order," or "show the manager the order page." If scanning can replace that repetitive step, WPC Order Barcodes can provide clear value.

Good Fit

• Stores with manual packing and pickup workflows where staff often open orders by number.
• Projects with reservations, tickets, or registration, if the WooCommerce order is used as the basis for access.
• Sites where it is useful for the customer to see the code in an email or on the order details page.
• Teams that want to place the scanner on a separate staff page using [wpcob_scanner].
• Developers and webmasters who need shortcode-based code output inside a template, page, or page builder.

May Not Be the Right Fit

If you need a full participant registration system with seat assignments, attendee lists, CSV export, recurring events, and separate ticket types, a single order barcode may be too narrow a solution. In that case, it makes more sense to look at event booking plugins or dedicated ticketing extensions. If you need QR codes for products, pages, marketing links, business cards, or arbitrary URLs, a general-purpose QR plugin will usually be a better fit than a tool focused on WooCommerce orders.

You should also test the plugin carefully if your site has a complex extension stack: custom order statuses, PDF invoices, custom email templates, aggressive JavaScript optimization, a separate warehouse app, external inventory/accounting, or automatic status handling from payment gateways. That does not mean WPC Order Barcodes will not work. It means the plugin's value needs to be verified against the real workflow chain: "order - email - code - scanner - staff action."

Practical rule: install WPC Order Barcodes on a staging copy or test store first. Create several orders with different statuses, check the email, thank-you page, customer account, and scanner. Only then should you roll the workflow into your live team process.

What to Check Before Installing It on a WordPress Site

Before installation, it is not enough to confirm that the site runs on WordPress and WooCommerce. You also need to understand exactly where the code will appear, who will scan it, and what data will open after the scan. Otherwise, you may end up with a technically working plugin that does not fit your store's actual process.

The official WPClever page lists requirements and compatibility with WordPress and WooCommerce, but this article should not treat version numbers as permanent facts. Before installing, open the product page and check the current Require, Compatible, and Last updated lines. If your store uses current WooCommerce versions, a custom theme, and multiple order-related extensions, that extra check becomes even more important.

Technical Preparation

• Make sure WooCommerce is active and the orders table opens without errors under WooCommerce > Orders.
• Create a backup or work on a staging copy, especially if the store is already processing live orders.
• Review staff roles: the scanner and order results should not be available to people who should not see customer personal data.
• Open your current WooCommerce email templates and check whether they are overridden by the theme or another plugin.
• Review caching and JavaScript optimization. A camera-based scanner in popup mode is not something you want to test on a page where every script is aggressively deferred without exceptions.
• Prepare a test device: a phone with a camera, a tablet, a laptop, or a handheld scanner if your warehouse already uses one.

Operational Preparation

It is just as important to align with your team on what counts as a successful scan. For a warehouse, that may mean opening the order quickly and verifying its contents. For pickup, it may mean confirming the customer name and status. For events, it may mean checking that the order is paid and has not already been processed. If you do not define the expected outcome in advance, staff may scan the code and still manually double-check everything the old way.

Create a short test memo. It should cover three things: where the code comes from, what device or tool is used to scan it, and what should open after the scan. That makes it much easier to tell the difference between a configuration problem and a mismatch in expectations. For example, if the code opens the order but the staff member expected the order status to change automatically, that is not a scanner error. It is an unaligned process assumption.

Mini Checklist Before the First Launch

1. Create or locate a test order that does not contain real personal data.
2. Decide which code type you want to test first: qrcode, code128, ean13, datamatrix, or code39.
3. Confirm where the code is supposed to appear: email, thank-you page, customer account, or a staff page with the shortcode.
4. Prepare the scanning device and check that the browser has permission to access the camera.
5. Write down the expected result: open the order, find the order, verify the status, or show information in a popup.

Installation and First Validation Without Risking Live Orders

Installing a commercial plugin usually means uploading a ZIP archive through the WordPress admin. The general logic is described in WordPress documentation: go to Plugins > Add New, choose the plugin upload option, install the archive, and activate it. If you received the file from your account area or a developer email, do not rename the plugin folder manually or upload the extracted structure unless there is a specific reason to do so.

After activation, do not immediately enable every display option. First, confirm that the site recognizes the plugin, WooCommerce opens orders correctly, and a test order receives a code. Since WPC Order Barcodes is tied directly to orders, the safest way to start is with a real test order, not by guessing from the homepage.

Basic Sequence

1. Open Plugins > Add New and upload the plugin ZIP through Upload Plugin.
2. Activate the plugin with Activate Plugin.
3. Go to the plugin settings if it adds a separate menu item or a tab inside WooCommerce.
4. Keep the default code type and default display positions for the first test so you are not changing multiple variables at once.
5. Create a WooCommerce test order or place a test purchase using a safe test payment method.
6. Open the order page in the admin area and check whether the code, or the place where it should appear, is visible.
7. Check the Order received page and the email if those output locations are enabled.

If the code does not appear, do not assume the plugin is broken. First, check whether the order was created after the plugin was activated. The official description says codes are generated automatically for new orders; for older orders, behavior should be verified on your installed copy. If older orders did not receive a code, create a new test order and see whether the result changes.

How to Tell the First Launch Went Correctly

The first launch is successful if three things are true. First, the new order gets a visually readable code. Second, the code appears where you enabled it. Third, the scanner or reading device returns the expected information without manual correction of the string. If even one of those conditions fails, troubleshoot the specific point in the chain instead of changing every setting at once.

Do not test everything on a single order. Create several test orders with different statuses, such as Processing, Completed, and On hold. That will help you quickly see whether code output depends on the status, email, template, or viewing context.

Detailed Setup: Code Type, Output Locations, and Shortcodes

Configuring WPC Order Barcodes comes down to three main questions: which code to generate, where to display it, and how staff will scan it. The official description lists several code types, configurable prefixes, output locations, and two core shortcodes. That is enough to build a practical setup without inventing features that are not documented.

Do not start with the most complicated option. For most stores, a sensible first profile looks like this: QR Code for a test order, display in the email and on the order view page, a separate staff page with the scanner, and popup mode only for tight areas such as a sidebar or menu. Once that works, you can test a linear barcode if your warehouse scanner works better with Code 128 or Code 39.

Choosing a Code Type

WPClever lists QR Code, EAN-13, Code 128, Data Matrix, and Code 39. Each format has a practical use case. QR Code is easy to scan with a camera and familiar to most users. Data Matrix is compact, but many stores will not need it. Code 128 is often chosen for warehouse operations because it works well with alphanumeric strings. Code 39 is simpler and broadly compatible, but less dense. EAN-13 is common in retail, but it is strict about data format, so you should verify in advance whether your code structure fits it.

After choosing the code type, do not change width, prefix, display position, and scanner mode all at once. First, confirm that the selected format is readable in your actual environment. Then adjust the size and output location.

Prefix and Value Structure

The official page mentions custom prefixes. A prefix is helpful if the same scanner is used for more than just WooCommerce orders. For example, it can visually distinguish an order from a warehouse bin, coupon, internal SKU, or ticket from another system. But the prefix should be short and consistent. A long string increases code density, reduces readability, and makes manual checking harder.

For the first run, use a clear prefix such as ORD, or leave the value without a prefix if the process only deals with orders. After testing, decide whether staff actually benefit from having one. If they never see the raw string and the scanner immediately opens the result, the prefix may be unnecessary.

Output Locations: Email, Thank-You Page, and Customer Account

WPC Order Barcodes can display codes in order emails, on the Order received page, and on customer View Order pages. These are three different contexts. Email is often printed or forwarded. The thank-you page appears immediately after checkout. The customer account is useful when the buyer needs to come back later and show the code at pickup.

Do not enable every location without thinking it through. If the code is meant only for warehouse staff, putting it in the customer email may add unnecessary noise. If the code is needed for event entry, the email and customer account are both useful. If the code belongs only on an internal packing slip, check whether your PDF or packing slip plugin supports the required shortcode or template insertion. If that is not confirmed, do not promise the integration to a client until you have tested it.

What to Check After Saving Output Locations

1. Create a new test order so you can rule out issues caused by old data.
2. Open the order email in a mailbox and review the code on both desktop and mobile.
3. Open the thank-you page immediately after the test purchase.
4. Log in as the test customer and open the order details page.
5. Scan the code from the screen and from a printout if printing is part of the workflow.

Shortcode for Displaying the Order Code

The official [wpcob_barcode] shortcode accepts several attributes. order_id sets the order ID; if you omit it, the shortcode displays a sample barcode, which is useful for preview purposes. code_type lets you override the code type for a specific location. width sets the scale or width. That is helpful when one format is selected in settings but you want to test another one in a specific template.

[wpcob_barcode order_id="123" code_type="qrcode" width="200"]

On a real article page, page, or widget, you should never insert a random order ID. If the shortcode is used on a restricted staff page, access to that page must be limited. If the shortcode is inserted into a template, check where the order ID comes from and make sure an unauthorized user cannot see another person's order data. Without confirmed hook documentation, the safer path is to use the shortcode only in places explicitly supported by the product and the WooCommerce context.

Scanner Shortcode and Popup Mode

The second official shortcode is [wpcob_scanner]. It outputs the scanner and supports the display_result attribute with the values inline and popup. Inline mode works well on a dedicated staff page where the result should appear directly beneath the scanner. Popup mode is useful in tighter layouts, for example when the scanner sits in a sidebar, sticky block, or another container where the camera preview and result could break the page layout.

[wpcob_scanner display_result="popup"]

For the first test, create a restricted page such as "Order Scanner" and insert the shortcode there. Do not place the scanner in a public menu until you have verified both access control and the returned result. Even if the shortcode displays correctly, the browser usually requires camera permission and a secure site context. If the page is opened on an insecure URL or the browser blocks camera access, staff will see an environmental limitation, not a plugin failure.

Order Scanner: How to Build It Into Your Team Workflow

The scanner is the most practical part of WPC Order Barcodes, but it is also the feature most likely to reveal weak points in your process. It is one thing to see a code in an email. It is another to give a staff member a page where they can scan orders quickly, understand the result, and avoid getting access to unnecessary data. That is why the scanner should be designed as an internal operations tool, not just dropped into the first page where a shortcode happens to fit.

The best place to start is a separate page available only to administrators or store managers. In WordPress, that can be handled with a private page, user role restrictions, membership controls, or an internal site section. The exact method depends on your setup, so this guide should not promise universal protection from a single shortcode. WPC Order Barcodes is responsible for displaying the scanner; the site owner is responsible for restricting access to both the page and the order data.

Inline or Popup

Inline mode shows the result directly in the page flow. It works well when the staff member is using a large screen or tablet and the whole page is dedicated to scanning. Popup mode is better when the scanner sits in a narrow area where the result could break the layout. The official description specifically highlights popup mode as useful for tight layouts, headers, sidebars, and sticky menus.

For an internal staff screen, it is usually better to start with inline because the result is easier to monitor. Popup mode makes sense only after you know scanning works and the only real issue is page layout. If you start with popup immediately, it becomes harder to tell whether the problem is the camera not opening, the code not being recognized, the result not fitting, or an overlay conflict with the theme.

Access Rights and Personal Data

A WooCommerce order may contain a name, address, phone number, email, products, payment method, shipping details, and notes. That is why the scanner page should never be public. Even if the code itself looks like a technical string, scanning it may lead to information that should not be visible to a random visitor. Grant access only to roles that are already allowed to work with orders.

If the scanner is meant for pickup staff, you do not have to give them full administrator access. Check whether the store manager role is enough, or create a separate role using a trusted role management plugin. Do not create one shared administrator account for all staff. That makes activity auditing harder and increases the risk of data leaks.

Camera, Browser, and Device

The scanner depends on more than just the plugin. The browser must allow camera access, the device must be able to see the code clearly, the page must not be blocked by security policies, and there must be enough light. If a staff member is using an outdated Android browser, an in-app messenger browser, or a corporate device with camera restrictions, the problem may show up as "the scanner does not work" even though the shortcode itself is fine.

Quick Device Test

1. Open the internal scanner page in a regular browser, not inside a messenger app.
2. Allow camera access when the browser asks for permission.
3. Scan the code from the order screen and from a printout.
4. Check whether the staff member sees the expected data and can complete the next action.
5. Repeat the test in low light and at the real scanning distance used in daily work.

If the scanner will be used every day, standardize the device, browser, and page URL in your internal instructions. A repeatable process matters more than a one-time successful test.

Practical Example: Releasing a Paid Order by QR Code

Now let us build a concrete scenario. Imagine a store with local pickup: the customer places an order on the site, receives an email, arrives at the pickup location, and shows the code from the email or customer account. A staff member scans the code, opens the order, verifies the status, and hands over the item. This scenario does not require a complex ticketing system, but it benefits from faster order lookup.

Goal

The goal is to let pickup staff find the order by scanning instead of manually searching by order number, name, or phone number. A secondary goal is to avoid showing the code where it is not needed and to keep random users away from the scanner page.

Preparation

• WooCommerce is installed, orders are created normally, and they are visible under WooCommerce > Orders.
• WPC Order Barcodes is activated and configured to generate a QR Code for new orders.
• The code is enabled in the customer email or in the View Order section if the customer needs to present it.
• A restricted staff page with the scanner [wpcob_scanner display_result="inline"] has been created.
• The staff member has a role that allows access to the necessary order details.

Steps

1. Create a low-cost test product or use a safe test payment method.
2. Place a test order as a customer and move it to the status that means "ready for processing" in your store.
3. Open the order email and make sure the code is visible, not cropped, and not too small.
4. Log in as a staff member, open the restricted scanner page, and allow camera access.
5. Scan the code from the email or from the customer order page.
6. Verify that the result points to the correct order: order number, test customer name, order contents, and status.
7. After pickup, change the order status using your normal WooCommerce procedure if that step is part of your store workflow.

Expected Result

The staff member should be able to move quickly from the code to the order and see enough information to make the right decision: release the order, request payment, verify contents, pause the handoff, or escalate to a manager. If they still end up searching manually after scanning, the workflow is not complete. At that point, you need to clarify what exactly the scanner returns and whether that result is sufficient for the actual task.

The Detail People Often Miss

The code itself does not equal permission to release the order. It helps staff find the order quickly. The actual handoff decision should still depend on the order status, payment, order contents, and your store's internal rules. If a customer shows a code from an old email for a canceled or refunded order, staff must check the status instead of trusting the QR code alone.

Result check: the test is successful not when the camera reads the code, but when the staff member completes the actual job faster and without unnecessary manual searching.

Validating the Result in Email, the Customer Account, and the Admin Area

After setup, you should walk through the entire order journey. WooCommerce documentation on emails points out that email issues are often caused not only by WooCommerce itself, but also by wp_mail(), template settings, order statuses, plugins, and deliverability. For WPC Order Barcodes, that means if the code is missing from an email, you need to determine whether the email was sent at all, whether the template is disabled, whether the email HTML is overridden by the theme, and whether the HTML gets cut off.

Email Check

First, make sure the email is actually being generated. Orders with the Pending Payment status may behave differently from paid orders, and some emails can be turned on or off in WooCommerce settings. Open WooCommerce > Settings > Emails and review the required template. Then create a new test order and inspect the email in a real inbox.

The code should be visible without horizontal scrolling, should not turn into a tiny blurred block, and should be scannable from the screen. If customers may print the email, print it on a standard printer. Confirm that the contrast is sufficient and the code stays readable after scaling.

Thank-You Page Check

The Order received page appears immediately after checkout. It is useful when the customer needs to save or show the code right away. But that page is often seen only once, after which the user returns to the order through email or the account area. So if your workflow requires repeated access, do not make the thank-you page the only place where the customer can get the code.

Customer Account Check

The View Order page in the customer account is ideal for showing the code again later. Test it as the actual customer, not as an administrator. That way you will see how the code appears in the real customer context, whether the display depends on the theme, and whether any extra internal information is leaking into view.

Admin Area and Orders Table Check

WooCommerce shows orders in the WooCommerce > Orders table, where staff can search, filter, and open order details. If scanning takes a staff member into the admin area, they should know which fields matter: order number, status, customer, contents, shipping, and notes. Add that sequence to your internal instructions. The scanner speeds up access to the order, but it does not replace processing rules.

Safe Visual Tweaks for the Code Without Editing the Plugin

With WPC Order Barcodes, you should not invent PHP hooks or edit plugin files. If you want to improve how the code looks in an email or on a staff page, start with reversible CSS. That is the safer approach: it does not interfere with code generation, does not change order logic, and can be removed easily if a plugin update changes the markup.

Because the official page does not document exact CSS classes for the output, the example below uses a neutral wrapper. The idea is simple: place the shortcode or code block inside a container with your own class and style only that container. That avoids depending on the plugin's internal classes and makes updates safer.

CSS for the Staff Scanner Page

Create a block on the restricted page where the scanner shortcode appears, and assign it the class order-scan-panel through the editor or template. Then add the CSS to your child theme or to the theme's built-in additional CSS section.

.order-scan-panel {
  max-width: 760px;
  margin: 24px auto;
  padding: 20px;
  border: 1px solid #d8dee4;
  border-radius: 8px;
  background: #ffffff;
}

.order-scan-panel .scan-note {
  margin-top: 12px;
  color: #4b5563;
  font-size: 14px;
  line-height: 1.5;
}

Inside the page, you can add a short note for staff:

<div class="order-scan-panel">
  [wpcob_scanner display_result="inline"]
  <p class="scan-note">Scan only codes for current orders. After opening the order, check the status and contents before handing it over.</p>
</div>

The validation is simple: open the page under a staff role, make sure the scanner does not exceed the container width, confirm the note is visible, and check that the camera still opens. Rolling back is simple too: remove the CSS and wrapper while keeping the shortcode itself. If your theme or page builder changes the HTML, style the outer wrapper class rather than the plugin's internal elements.

What Not to Do

• Do not edit WPC Order Barcodes files directly, because an update may overwrite your changes.
• Do not place the scanner shortcode on a public page without access control.
• Do not rely on CSS alone to hide sensitive order data if access should be restricted at the permissions level.
• Do not promise automatic status changes after scanning unless that behavior is confirmed in your version and documentation.

Limitations, Compatibility, and Performance Impact

Any plugin that works with orders, emails, and a scanning interface depends on the surrounding systems. In the case of WPC Order Barcodes, the most important factors are WooCommerce order statuses, email templates, access rights, browser camera permissions, and JavaScript optimization. If any of those layers is configured in a nonstandard way, the issue may look like a barcode plugin bug even when the real cause lives in the theme, email system, cache, or user role setup.

Email Templates and PDF Documents

The official page confirms output in WooCommerce emails. But that is not the same thing as automatic support for every PDF invoice or packing slip plugin. If you want to print the code on a packing slip, check the documentation for your specific PDF solution: does it support shortcodes, custom order fields, or template insertions? If that is not clearly confirmed, do not add it to your live process until you have tested it.

Caching and Script Optimization

The scanner page may depend on JavaScript and camera access. If your site uses script combining, deferred loading, or delayed execution, test the scanner separately. For a staff page, it is often reasonable to exclude that page from aggressive optimization if the camera stops opening or popup mode becomes unstable after caching is enabled. That is not a universal rule, just a diagnostic step: confirm the issue first, then add an exception.

HPOS and New Order Tables

WooCommerce is moving order storage into dedicated tables. For WPC Order Barcodes, rely on the current compatibility stated on the product page and test it on your WooCommerce version. If your store already uses High Performance Order Storage, create a separate test order after enabling the plugin and confirm that the code is generated, displayed, and scannable. Do not move the output into live customer emails until that test passes.

SEO and Indexing

Order codes should not appear on public, indexable pages. The scanner page, customer account, order view page, and staff-facing results should all be restricted from general visitors. This is not primarily an SEO concern. It is a privacy issue. Do not place a shortcode with a specific order_id on a public page if it could expose order-related information.

How to Train Staff to Work With Order Codes

Technically, WPC Order Barcodes can be enabled in a few minutes, but the real benefit only appears after a short team instruction. What staff need to understand is not the plugin name, but the action path: where to get the code, where to point the camera, which data to verify, when to change the status, and when to stop. Without that guidance, scanning easily turns into one more button that everyone ignores in favor of manual order search.

Start with one scenario and one role. For example, a pickup staff member opens the restricted scanner page, scans the code from the customer email, verifies the customer name and order contents, checks the status, and only then hands over the item. Do not add the warehouse, manager, administrator, and customer scenarios all at once. The fewer moving parts in the first workflow, the easier it is to see where the plugin helps and where the process itself is still undefined.

Mini Procedure for a Pickup Counter

1. Open the staff scanner page before the shift starts and confirm that the camera is available.
2. Ask the customer to show the code from the email or the order page in their account.
3. Scan the code and wait for the result instead of manually entering the order number.
4. Verify the order status, customer name, and pickup contents.
5. If the status is not appropriate for release, do not hand over the item and escalate the order to a manager.
6. After pickup, perform the store's standard status update or order note action.

This procedure does not need to be long. You can place it directly below the scanner shortcode as a short note or publish it on a separate internal page. The key point is not to mix order handling rules with technical plugin setup details. Staff do not need to know why you chose qrcode or code128. They need to know what to scan and what result counts as correct.

Manager Check Questions

After a few test shifts, review whether scanning is actually making the work faster. You do not need complex reports for that. Just answer a few concrete questions: are staff searching manually less often, are there fewer pickup mistakes, are canceled and unpaid orders handled clearly, and is there any confusion between the customer-facing code and an internal warehouse code.

If the team continues to rely on manual search, the barcode itself is usually not the real issue. There are usually three possibilities. First, the code is placed in an inconvenient spot, so the customer cannot quickly find it in the email. Second, the scanner opens a result that is not useful enough, so the staff member still returns to the orders table. Third, the status logic has not been documented clearly, so people do not know whether the order can be released after scanning. Fix the actual cause: move the code to a more visible place, improve the staff page, clarify the workflow, or train staff to check status.

How Not to Overload the Customer With Extra Codes

Customers do not always need to see the barcode. If the code is only for warehouse staff, adding it to the customer email may create confusion: "What am I supposed to do with this?" If the code is needed for pickup or entry, place a short human explanation next to it in the email or on the order page. For example: "Show this code to the pickup staff." There is no need to explain the code type, the shortcode, or the internal order ID.

Always check the email on a mobile screen. Most customers will open it on a phone, and the code should be visible without pushing out the main information: order number, products, total, and address. If the email becomes too long, keep the code in the customer account and add a link in the email to view the order instead. The right choice depends on how often the customer needs to return to the code and where they will actually show it.

Process Change Log

Whenever you change the code format, size, output location, or scanner mode, record it in a short internal log. You do not need elaborate documentation. Just note the change date, what was changed, why, and how it was tested. That helps if a staff member says a week later that the scanner "started behaving differently." You will be able to tell whether the change is related to a plugin update, an email template change, a cache setting, or a new device.

This log is especially useful for stores where several people work on the site: the owner, webmaster, marketer, warehouse staff, and outside contractor. WPC Order Barcodes touches several areas at once, so a small change in email markup or script optimization can show up as a scanning issue. The better the settings chain is documented, the easier it is to restore a working state.

Why the Code or Scanner May Not Work and How to Check It

Troubleshooting is best done as a chain: the order is created, the code is generated, the code is displayed, the code is readable, the scanner shows the expected result, and the staff member can complete the action. If you jump straight to reinstalling the plugin, it is easy to miss a simple cause: the email is disabled, the browser blocked the camera, the code is too small, or you tested an old order.

The Code Did Not Appear on a New Order

Symptom: the order was created, but the code is not visible in the admin area, email, or order page. Possible causes include the plugin not being active, output for the required location being disabled, looking at an old order, or a specific template not supporting that output position.

Check a new test order created after activation. Then enable only one output location and test it separately. If the code appears on the order page but not in the email, the issue is more likely related to the email template or email settings than to code generation itself.

The Code Exists but Will Not Scan

Symptom: the image is visible, but the camera or handheld scanner cannot read it. Possible causes include the size being too small, low contrast, the wrong code type, email compression, poor print quality, or scanner incompatibility with the selected format.

Increase the width through the setting or the width attribute, test QR Code and Code 128 separately, and print the code at its real working size. If QR Code scans on a phone but not on the warehouse scanner, verify whether the device supports QR at all. If the linear code is too wide to fit in the email, switch back to QR Code or give it a larger display area.

The Scanner Does Not Open the Camera

Symptom: the shortcode appears, but the browser does not show the camera or keeps asking for permission repeatedly. Possible causes include browser camera restrictions, an insecure page context, corporate device policies, a JavaScript conflict, or opening the page inside a messenger app browser.

Open the page in a standard browser, review the site permissions, temporarily disable script optimization for the staff page, and test on another device. If the scanner works on one device but not another, start with the browser settings and device policy.

The Wrong Result Opens After Scanning

Symptom: the code scans, but the staff member does not see the right data or lands on an unexpected order. Possible causes include testing a sample barcode without order_id, using an old printed code, the staff member lacking the proper permissions, or a prefix or value format that does not match the process expectation.

First, verify that the scanned code actually belongs to the test order. Then compare the value returned by the scanner with the order number or order ID. If the [wpcob_barcode] shortcode is used on a staff page, make sure it was not left in sample preview mode.

The Code Is Missing From a WooCommerce Email

Symptom: the code appears on the order page but not in the email. Possible causes include the email template being disabled, the order being in a status that does not send the needed email, the email not being sent through wp_mail(), the theme or a plugin overriding the email HTML, or the image being blocked by the email client.

Check WooCommerce > Settings > Emails, create a new order with the correct status, use an email log to confirm delivery, and temporarily compare the default email template with your custom one. If the default template shows the code and the custom one does not, the problem is in the template override.

Popup Mode Breaks the Layout or Does Not Close

Symptom: the popup scanner opens, but it overlaps other elements, does not fit on mobile, or conflicts with the menu. Possible causes include the theme using its own overlay layers, a sticky header with a high z-index, script optimization on the page, or a container that is too narrow.

Test inline mode on a separate page. If inline works reliably but popup does not, the problem is not the scanning itself but the wrapper around it. In that case, use a dedicated staff page or troubleshoot the theme conflict directly. The right rollback is to disable popup mode, not the entire plugin.

When WPC Order Barcodes Is the Right Choice

WPC Order Barcodes is worth using when you have a clear physical or operational point where an order needs to be found quickly by scanning. The plugin fits well into pickup, packing, reservation checks, registration, and internal warehouse workflows. Its strength is the combination of the WooCommerce order, barcode or QR code, shortcode-based output, and a scanner page.

Before rolling it out, do not promise the team "warehouse automation" from a single installation. First, define the workflow, choose the code format, create a restricted scanner page, verify the email and customer page, test several orders with different statuses, and only then move the process into daily use. If all of that lines up, you can download the WPC Order Barcodes archive and test it safely on your site.

If instead you need a universal QR builder, an advanced ticketing system, PDF invoices with custom templates, or a complex integration with warehouse software, start by comparing alternatives. WPC Order Barcodes works best as a focused tool for WooCommerce orders, not as a replacement for every inventory, ticketing, and logistics process.