WooCommerce Memberships is not just another plugin for restricting your site’s content: it’s an easy-to-use, site-wide membership solution that brings your content, shop, and memberships together.

Memberships allows you to create an entire membership system that’s seamlessly tied to your store.

You can restrict your content to members, but you can also “drip” that content over time to schedule when members have access. Sell access to memberships, include memberships with product purchases, manually assign memberships, and completely integrate member perks within your store.

Sell or Assign Memberships

Memberships are not a specific type of WooCommerce product; instead, membership plans are created independently from products. This lets you determine how access is granted for maximum flexibility. You can assign 0 or more products (of almost any type) to a membership plan to support several types of memberships:

• sell a membership as stand-alone product — create a product for the membership, then tie the plan to that product to sell it
• grant access to a membership as part of a product purchase — i.e., buy a subscription for a meal box, get access to the recipes section for free
• grant access to the same membership from several products (i.e., a yearly purchase or a monthly subscription)
• assign memberships manually for an invite-only members area

  

Strategically Grant Content Access

You put a lot of work into your members-only content, so Memberships lets you schedule when your members should have access to it. You can drip content, which means that you can schedule when members should have access to your content. For example, you can require that customers be a member for a week before they can access certain posts or pages.

This gives you more control over how members begin using your site and lets you introduce members to your content at your pace.

When you use this with Subscriptions, you can even determine which content is included in a free trial period with content dripping rules.

Turn Your Store into a Purchasing Club

Memberships lets you create members-only products so that your site can become a purchasing club, or let you offer certain products exclusively to members.

You can restrict product viewing to members, which means these products will be hidden from non-members in your shop. You can also restrict purchasing, which means that products are public, but only members can buy them.

You can also drip product access so that members don’t get access to products immediately.

Offer Better Shipping Options to Members

Members should be your most loyal customers, so giving them perks that encourage them to purchase repeatedly from you keeps them coming back for more. Memberships extends your free shipping settings so you can offer free shipping directly to your members, while requiring non-members to meet other criteria (like having a coupon or minimum order amount).

Reward Members with Special Discounts

Since you may want to give your members certain perks, you can provide member discounts for all products, some products, or certain product categories.

Automatically Show Members Their Perks

While membership management should be easy on you, it should be easy on your members, too. Members can find all of the information they need about their memberships in the Member Area. Members can access the area for any membership from the “My Account” page by clicking “View”.

You can enable any or all sections of the member area to show members a list of accessible content (post and pages), products, discounts, and / or public membership notes. If a member will have access to content in the future, the member can see the access date as well.

Import or Export Members

You have a lot of tools to manage members within WooCommerce, but you may want to connect to other services too, such as importing a member list into an email tool. Memberships lets you export members to a CSV file so that you can get member data out of WooCommerce and into other tools.

You can also import members via CSV to add new memberships, create new users, or bulk-update existing members by merging your file with existing data.

Simplify Communication with Members

When you run a membership site, you spend a lot of time on customer service and managing members. We’ve tried to make that as easy as possible with Memberships. We’ve added “Membership Notes” so that you can track information about memberships for a customer, add your own notes for your reference, and even easily communicate with a particular member by sharing a note with them via email.

You can also use expiration and renewal reminder emails to let members know of ending memberships and prompt them to renew or upgrade.

Memberships + Subscriptions

Memberships is fully functional as a stand-alone membership solution, but it works very well with the most advanced eCommerce recurring payments solution available: WooCommerce Subscriptions.

When both plugins are active, Memberships can leverage some features of Subscriptions to give you more flexibility over membership billing (more details in our documentation):

• Memberships can use recurring billing (i.e., monthly payments) for the membership rather than a set term (such as a year)
• Memberships can use Subscriptions as a payment plan, but control access length itself to support installment payments
• Free trials can be used for the membership via a subscription
• Content restriction and dripping can include or exclude free trial periods so you control what content is available in trials
• Members can pause their own memberships by suspending a subscription
• Members can upgrade or downgrade memberships by switching a subscription
• Upgrades and downgrades can leverage Subscription’s proration to ensure that membership costs are accurate

Even if you don’t want to use recurring billing, you can leverage the other features of Subscriptions by setting the subscription length to one billing cycle so you can take advantage of upgrades and downgrades or trial periods.

Selling Memberships to Companies or Groups

Need to sell memberships to teams, companies, or groups instead? Check out the Teams for WooCommerce Memberships extension (purchased separately). This plugin adds on to WooCommerce Memberships, letting to sell access to a group of users instead of an individual.

How to Get Started

Ready to create memberships for your customers? You can get going with these steps:

1. Buy this extension 
2. Download and install Memberships in your WooCommerce store
3. Create your Membership Plans and Members
4. Check out our extensive documentation for any advanced setup help
5. That’s it! Sit back and enjoy your fully integrated membership site!

The post WooCommerce Memberships first appeared on CODIBU.

The table rate shipping module extends WooCommerce’s default shipping options giving you highly customizable shipping options.

Define multiple shipping rates based on location, price, weight, or item count. Wildcards may be used to match multiple regions too.

• Add multiple tables of rates per shipping zone
• Several types of table rate calculation: Per order, Calculated per item, Calculated per line, Calculated per class
• Add rules based on Weight, Number of items, Number of items by class and Price
• Add costs per row, per item cost, a percentage and per weight unit

Intuitive Interface

Adding data as complex as table rate shipping can be an arduous process. That’s why the user interface has been designed to make the process of adding, duplicating and removing rates as intuitive as possible.

The post Table Rate Shipping first appeared on CODIBU.

For a shopping experience as unique as your customers

From adding a personal engraving, to upgrading to premium fabric, customizing products can keep your customers coming back. With Product Add-Ons, you can offer special options to your customers in a snap.

Product Add-Ons allow your customers to personalize products while they’re shopping on your online store. No more follow-up email requests—customers get what they want, before they’re done checking out.

Add options via text boxes, dropdowns, text areas, checkboxes, custom price inputs, even sample images. Add-ons can be added globally or per-product from the edit product page.

Give your customers the options they want

Product Add-Ons is one of the most popular extensions available for WooCommerce. It gives you and your customers even more options, including (but definitely not limited to):

Image-based selections

A picture’s worth a thousand words, so why describe a customer’s personalization options when you can show them? With image-based selections, customers can see what they’re getting before they buy.

Flat fees

Charge customers a flat fee regardless of how many products they ordered. Perfect for a one-time set-up charge or a rush fee.

Percentage fees

Charge a fee for the add-on based on a percent of the total price—this is especially useful for service-based add-ons that can be tougher to boil down to a flat fee.

Text input

Let your customers enter custom text to create a custom t-shirt, add a monogram or personalize a card.

Dropdown

Customer can chose between a few pre-defined options with a drop-down field for your add-on.

Checkboxes

Make customization as easy and satisfying as checking a checkbox. Great for add-on services, like gift wrapping or express shipping.

Custom price

Let your customers name their price, perfect for tips, donations and gratuity!

Add-ons can be named, described, reordered and (optionally) given prices.

The extension also works with:

• WooCommerce Subscriptions – add additional options to subscription products.
• WooCommerce Bookings – offer upgrades like an oil treatment for a massage, priority seats for their tour or a rush fee for their rental.

The post Product Add-Ons first appeared on CODIBU.

The WooCommerce Customer / Order / Coupon Export extension lets you export your site’s customers, orders, or coupons to a CSV or XML file. Here are a few of the features offered by this plugin to make it easier to manage your site’s data:

• Export customers, orders, or coupons, in CSV or XML format, individually or in bulk.
• Create your own custom formats to determine which fields are included and where they’re positioned.
• Automatically export and send your file to a remote server via FTP, HTTP POST, or email, such as to your fulfillment service.
• Exports run asynchronously in the background, meaning you can export thousands of records while you complete other tasks – or take a well-earned break!

 Click here to read our developer documentation.

If you want to export orders to Stamps.com, please check out the Stamps.com XML File Export extension instead!

 Free add-ons available!

 

• Export refunded orders only
• Export the customer VAT number – requires the WooCommerce Taxamo or EU VAT Number plugin.

 

Requirements

• PHP 5.6+ (you can view this under WooCommerce > Status)
• WooCommerce 3.0.9+
• Your site must support background processing to use automated exports or process exports in the background of your site. Click here to learn more about this requirement.

Installation

1. Ensure your store meets the plugin requirements.
2. Download the extension from your WooCommerce dashboard.
3. Go to Plugins > Add New > Upload and select the ZIP file you just downloaded.
4. Click Install Now and then Activate.
5. That’s it! You’re all set. Keep reading this documentation to learn more about exporting customers, orders, and coupons from your site!

Upgrading from another plugin

If you’re upgrading from the XML Export plugin, you will see a notice in the most recent version of that plugin to migrate to this version. Your existing plugin subscription has automatically been converted to a subscription for the unified Customer / Order / Coupon Export plugin! You can migrate your site to this plugin seamlessly with a couple of clicks.

You should be connected to WooCommerce.com to completed this migration. If your site isn’t connected, you’ll be prompted to connect first. If you need help connecting, please check out this document. If you can’t connect for some reason, please check our FAQs below for instructions on how to upgrade.

Once your site is connected to WooCommerce.com, you’ll see a notice to migrate to this plugin when you’re ready. With a single click, we’ll automatically take care of the full migration:

• The Customer / Order / Coupon Export plugin wil be downloaded from your WooCommerce.com account
• The plugin will be installed and activated on your site
• Your previous exports, custom formats, and automated export (if applicable) will be migrated from the XML Export plugin to this plugin

Upgrade FAQs

Q: What if I’m unable to connect to WooCommerce.com? (For example, if your site sells CBD oil products.)
A: You can still migrate! You’ll need a couple more steps, though:

1. Download the Customer / Order / Coupon Export plugin from your WooCommerce.com account (you will already have a new subscription for it).
2. Install this plugin under Plugins > Add New > Upload.
3. Activate this plugin.

Once this new, unified plugin is activated, it will handle migrating your settings automatically for you.

Q: What will happen to my XML Export plugin subscription?
A: Your WooCommerce.com account was automatically gifted a new subscription for this plugin. Here’s how we handled the change:

• You have been gifted a subscription for this plugin that ends on the same date as your XML Export plugin subscription.
• If your XML Export subscription was set to auto-renew, we’ve turned it off, and enabled auto-renew on the new plugin subscription. If your subscription did not auto-renew, we’ve left it disabled.
• Your XML Export plugin subscription is still in your account for now, but it will end on its original date, and cannot be renewed again.

Q: What if the migration doesn’t go smoothly?
A: The worst-case scenario is that we’re not able to migrate the plugin’s settings, and you would need to update them manually. This is a pretty foolproof process, though, that we have used for other plugin retirement migrations. Our support team is also happy to help out with any questions or migration concerns!

Export data manually

You can export customers, orders, and coupons manually at any time. When you begin a bulk export or export items from the Orders or Users lists, a modal will appear to let you know the export is processing:

If you leave this modal open while the export processes, you can download the file via that modal:

However, since customer and order exports are processed asynchronously in the background on your site, you can feel free to close the modal or leave your site completely while the export runs. This lets you keep working while your export processes behind the scenes. Exports are batch-processed, which allows your site to process an export for thousands of records without timing out.

If you leave the export modal, you can download the file from an admin notice that will appear when the export is ready or by going to WooCommerce > Exports > Export List, where we store exports for 14 days.

Exporting data in bulk

To manually export data in bulk:

1. 1. Go to WooCommerce > Export.
   2. On the Manual Export tab, update the following settings:
      • Output type: Choose to export your file in CSV or XML format.
      • Export type: Choose whether to export orders, customers, or coupons.
      • Format: Select a predefined or custom format.
      • Filename: Enter a name for the file generated by this export.
      • Mark as exported: Enable to ensure the exported data is excluded from future exports. Click here to learn more about this setting.
      • Batch processing: Only enable if your site does not support background processing.

1. Update the Export Options section to target particular orders (and include order notes), customers, or coupons. The available options will change based on your selected Output type.
2. If you have WooCommerce Subscriptions activated on your site and you’re exporting orders, you can also choose to export subscriptions orders only.
3. Click Export.

You can download the export file as explained above.

Exporting data from the Orders list

You can export one or more orders from the Orders page by following the steps below:

1. 1. Go to WooCommerce > Orders.
   2. Select one or more orders to export. You can set the Exported filter to show orders based on their export status.

1. 1. From the Bulk Actions menu, choose one of the following actions:
      • Download to CSV
      • Download to XML
      • Export and Send: Export the selected orders and send them via FTP, HTTP POST, or email.

1. Click Apply.
   • • If you selected an immediate download (e.g. Download to CSV or Download to XML), you can retrieve the download file as explained above.
     • If you chose Export and Send, you’ll be prompted to select one of your automated order exports so the same transfer method can be used to send this export. Only automated order exports with FTP, HTTP POST, or email transfer methods can be selected for this type of export.

   

Once an order is exported from the Orders page, it will be marked as exported. This will prevent the order from being included in future automated exports. Click here to read more about this setting and how to change it.

Exporting data from the Users list

You can export one or more customers (i.e. users that have made at least one purchase) from the Users page by following the steps below:

1. 1. Go to Users and select one or more customers to export.
   2. From the Bulk Actions menu, choose one of the following actions:
      • Download to CSV
      • Download to XML
      • Export and Send: Export the selected customers and send them via FTP, HTTP POST, or email.

1. Click Apply.
   • If you selected an immediate download (e.g. Download to CSV or Download to XML), you can retrieve the download file as explained above.
   • If you chose Export and Send, you’ll be prompted to select one of your automated order exports so the same transfer method can be used to send this export. Only automated customer exports with FTP, HTTP POST, or email transfer methods can be selected for this type of export.

Once an order is exported from the Users page, it will be marked as exported. This will prevent the customer from being included in future automated exports. Click here to read more about this setting and how to change it.

Export data automatically

If your site supports background processing, you can create one or more automated exports to send customer or order export files on a recurring basis.

Before you get started, please read the following notes about automated exports:

• Orders placed / customers created before activating this plugin will not be automatically exported. They can, however, be marked as exported if you’d like.
• Only items marked as not exported will be included in automated exports. Click here to learn more.
• Exports are scheduled in your WordPress site’s timezone. You can find your timezone settings under Settings > General.

Create an automated export

You can create an automated export by following the steps below:

1. 1. Go to WooCommerce > Export > Automated Exports and click Add New.

1. 1. Update the following settings for the automated export:
      • Enabled: Turn the automated export on or off.
      • Export name: Enter an internal name for the export.
      • Output type: Choose to export your file in CSV or XML format.
      • Export type: Choose whether to export orders, customers, or coupons.
      • Filename: Enter a name for the files generated for the export.
      • Format: Select a predefined or custom format.

1. 1. Update the Trigger automated export setting to determine when the export will run. Click here to read more about scheduling.
      • You can run order exports as orders or paid or on set intervals.
      • You can only run customer exports on set intervals.
   2. Update the Method setting to determine how the export will be sent / transferred. Click here to read more about transfer methods.

1. If you’re exporting orders, you can update the Export Options section to target particular orders and include order notes.
2. Click Save.

You can return to the Automated Exports tab to view and manage your automated exports.

Export schedules

This plugin relies on WP-Cron (the established way of performing recurring tasks within WordPress) to schedule automated export jobs. Unfortunately, the WP-Cron system is not always perfectly accurate – it requires constant traffic to your site to trigger events at the right times, which can be difficult for sites with less traffic.

There are two workarounds for this accuracy issue:

• Setup a real system cron on your server that ensures WP-Cron is triggered every minute. Click here to learn about setting this up. Your hosting provider should be able to help with this workaround, which would be ideal since it’s guaranteed to solve the issue with random times.
• Use a service (e.g. Pingdom or UptimeRobot) to ping your site every few minutes. This will ensure WP-Cron fires regularly.

Export transfers

Transfer methods

There are four methods you can use to transfer automated exports:

• Locally
• FTP
• HTTP POST
• Email

The FTP, HTTP Post, and Email methods include a test feature that you can use to confirm that everything is setup properly before activating the automated export.

Locally

Exports transferred locally are available for 14 days in the Export List. There’s no special setup required for this transfer method.

FTP

To transfer via FTP, you’ll need to update the following settings:

• Server address: Enter an IP address or hostname for the FTP server.
• Username
• Password
• Port: Enter “21” for regular FTP, “22” for SFTP, or “990” for FTP with Implicit SSL.
• Initial path: Enter the initial path for the FTP server without a leading slash and with a trailing slash. If you’re connecting via SFTP, the initial path should be the full path of the folder if your username doesn’t default to the HOME directory.
• Security: Choose your FTP server’s security.
• Passive mode: Enable to turn on passive mode for FTP connections. This should be disabled unless you are having issues connecting, especially if you’re seeing the PORT command successful message followed by a timeout in the error log (WooCommerce > Status > Logs).

HTTP POST

To transfer via HTTP POST, you’ll need to enter the HTTP POST URL where the export file should be sent. This is a great option for sending files to Zapier.

Email

To transfer via email, you’ll need to update a few settings:

• Recipient(s): Enter one or more (comma-separated) emails that should receive the export. If left blank, the export will send to the site admin’s email address, which is shown in the field’s tooltip and can be edited by going to Settings > General.
• Email subject: Set a subject line for the export email to help recipients identify the export file.

Transfer monitoring

When you configure automated exports, the plugin will track the transfer status of each export under the Export List. If a transfers fail, any site user who can manage WooCommerce (typically admins and shop managers) will be notified via admin notice.

If several failures occur consecutively, an admin notice will recommend checking out the logs and export settings to ensure the automated export is setup properly.

Marking data as exported

Because this plugin supports manual and multiple automated exports, it’s important to consider what will happen to an order or customers after export. This is especially important for stores that send automated exports to external sources. You wouldn’t want to include the same order in multiple automated exports to your fulfillment center, but you also wouldn’t want to exclude that order from an automated export if you exported the order manually for some other purpose.

To give you complete control over what data are included / excluded from your exports, we’ve included the ability to change export status (i.e. whether an item was exported or not) both at a global level (e.g. impacts all your exports) or for individual automated exports.

What happens when something is exported?

When you manually export an order or customer, it is marked as exported and will be excluded from all future automated exports. However, the order or customer will be included in future manual exports. If you do not want your manual export to impact future automated exports, be sure to disable the Mark as Exported setting before exporting.

When you automatically export an order or customers, it is marked as exported for that automated export and will be excluded from future runs of that automated export only. This prevents you from sending the same order over and over again to your fulfillment center.

How can I change whether something is marked as exported?

You can mark orders / customers as exported or not exported from a few locations.

• • Orders or Users lists. Use the Mark as Exported or Mark as Not Exported bulk actions to change the export status for the selected objects. This will change the export status for all exports.

• • Order detail or User detail pages. Select a specific order or user to toggle the export status at a global level (i.e. impacts all exports) or for one or more automated exports. This lets you determine whether an order or customer should be included in particular future automated exports.

Export formats

We offer several predefined formats, but you can also create your own custom format to ensure the file format meets your exact specifications.

Predefined formats

You can use one of our predefined formats to export your customers, orders, and coupons. The CSV Import formats are compatible with our Customer / Order / Coupon CSV Import Suite plugin.

Customer exports

• Default CSV format
• Default XML format
• CSV Import format

Order exports

• Default CSV format
• Default – One row per item CSV format
• Default XML format
• CSV Import format

Coupon exports

• CSV Import format

Create custom formats

You can create multiple custom export formats, which are useful if you need to rearrange, remove, or add columns to your export. Custom formats can be used in your manual or automated exports.

Custom CSV format

Follow the steps below to create a custom CSV export format:

1. 1. Go to WooCommerce > Exports > Custom Formats.
   2. Select the export type you want to create – Orders, Customers, or Coupons.
   3. Click Add new CSV format.

1. 1. Select an existing format to use as a starting point for your custom format and click Load, or click X to start from scratch.
   2. Update the Format Options:
      • Name: Enter an internal name for your export format.
      • CSV delimiter: Select a delimiter to separate columns in your file.
      • Include all meta: Choose whether to include all meta in the export. Click here to learn more about adding meta to exports.
   3. If you are creating an orders export format, you can also update the following extra options:
      • A row represents: Choose whether a row should represent a single order or a single line item (e.g. an order with multiple line items will span multiple rows).
      • Item columns should use: Choose whether items columns (e.g. line items) should be pipe-delimited or JSON format.
        • JSON example: typically used in the predefined CSV Import format for orders – [{"product_id":99,"product_name":"Woo Album","quantity":1,"total":19.99}]
        • Pipe-delimited example: typically used in the predefined Default CSV format for orders – product_id:99|sku:woo-album|name:Woo Album|quantity:1|total:19.99
   4. Update the Column Mapping to determine which fields will appear on your export.
      • When adding columns, the data source determines what data will appear in the export. You can select an option from the list, add a custom meta key, or add a static value.
   5. Click Save.

Custom XML format

Follow the steps below to create a custom XML export format:

1. 1. Go to WooCommerce > Exports > Custom Formats.
   2. Select the export type you want to create – Orders, Customers, or Coupons.
   3. Click Add new XML format.

1. 1. Select an existing format to use as a starting point for your custom format and click Load, or click X to start from scratch.
   2. Update the Format Options:
      • Name: Enter an internal name for your export format.
      • Indent output: Enable to pretty print the XML output with indents, which is helpful if a human is reading the file but unnecessary otherwise.
      • Include all meta: Choose whether to include all meta in the export. Click here to learn more about adding meta to exports.
   3. Update the Column Mapping to determine which fields will appear on your export.
      • When adding columns, the data source determines what data will appear in the export. You can select an option from the list, add a custom meta key, or add a static value.
   4. Click Save.

Adding custom meta

You can add columns for order, coupon, or user meta to custom formats.

To add custom meta, select “Meta field…” from the Data source drop-down menu and enter the Meta key.

You must know the correct meta key for the data when adding a column for meta. If you’re not sure, running an export with the Include all meta setting enabled will include all meta keys, so you can use that to find the meta key you want to include in your custom format going forward.

Adding static values

You can add columns for static values to custom formats. You can use this feature to add blank columns or columns with a set value for all rows (e.g. your store’s name).

To add a static value, select “Static value…” from the Data source drop-down menu and enter the Value.

Compatible plugins

This is a list of plugins (though not an exhaustive one!) that are known to be compatible with WooCommerce Customer / Order / Coupon Export. Columns are automatically added for plugins in this list; they are compatible out-of-the-box.

Frequently asked questions

Q: Can I export refunds?
A: Yes! This plugin is compatible with refunds while using one of the predefined formats or custom formats if the following fields are added:

• refunded_total: The amount refunded in the order
• Item_refunded: The total refunded for a particular item in the order

Q: There are users missing from my customer export. Where are they?
A: Users must place at least one order before they will be considered “customers” and included in this export.

Q: Can I duplicate columns in my custom export format?
A: No, we automatically remove all duplicate sources because columns are used as keys for the column headers.

Q: Can I remove the Export Status column from the Orders or Users pages?
A: Sure thing! You can hide this column (and many others!) by going to the Screen Options pages at the top of these screens.

Background processing

Q: How can I tell if my site supports background processing?
A: Go to WooCommerce > Status > Tools and run the Background Processing Test. If your site fails this test, please contact your host to enable background processing / loopback connections. While some hosts may identify this as a security issue, there’s no threat to using loopback connections and, if done properly, it won’t increase server usage. Quality hosts will mitigate increased server usage with rate limiting.

Q: My site doesn’t support background processing – do I need this to use the plugin?
A: Strictly speaking, no – you can still run exports without background processing enabled for your site.

However, background processing is required to run automated exports. Additionally, without background processing, you can’t leave the export modal while running a manual export. So while it’s not required, we highly recommend it for the best experience with this plugin!

More importantly, many current and upcoming features in WooCommerce need loopback connections to function. For example, the database updater (already in use) and future plans for backgrounded email sending, both of which uses the same type of background processing (and requires loopback connections). It’s essential that a host for an eCommerce site support this.

Excel display issues

Q: Why are leading zeros (e.g. in a ZIP code) missing from my Excel export?
A: By default, Excel hides leading zeros. This is most common with ZIP codes like “02111” – Excel will automatically hide the first zero and display “2111”. However, the zero is included in the export – you can force Excel to show this by formatting the column as “Text”.

Q: Why are the foreign / special characters not displaying correctly in Excel?
A: We’ll need to force Excel to use UTF-8 encoding to render these characters properly by adding this snippet to your site – please be sure you know how to safely add custom code to your site before adding this snippet:

add_filter( 'wc_customer_order_csv_export_enable_bom', '__return_true' );


Q: How can I ensure that Excel won’t show all my data in one column?
A: It sounds like your computer is setup to use a different delimiter than the standard comma. In most cases, the alternative delimiter is a semicolon. You can change delimiters in your export format.

XML format questions

Q: Can I separate Product Add-Ons in the XML file so they’re easier to find?
A: Unfortunately, the way that Product Add-Ons are stored on orders makes it nearly impossible to accurately get all add-ons for an order, so we do not support this for XML exports. However, we do have a code snippet available that should work for most stores, but please be sure you know how to safely add custom code to your site and test this thoroughly!

Q: Can I change the character encoding or XML version? My site uses special characters.

A: Absolutely! The defaults should work for most sites, but if you need to filter the character encoding, standalone definition, XML version, or other format definitions, you can do so using the wc_customer_order_export_suite_format_definition filter. Here’s a sample snippet to get you started – please be sure you know how to safely add custom code to your site before installing this snippet!

Troubleshooting

Here are a few common troubleshooting topics that we’re addressing in this section:

• Another plugin’s data isn’t showing up in the export
• Exports are remaining queue / freezing
• Exports are slow / receiving out-of-memory errors
• SSH2 Extension is not installed, cannot connect via SFTP
• Other issues

Incompatible plugins

There are a few plugins that are incompatible with this plugin:

• Product Add-Ons: While add-on data will be displayed in line item meta when exported, the plugin does not show add-ons separately for each line item.
• WooCommerce Bookings: Version 1.10.0+ changed the way booking data is related to an order. Because booking data are no longer part of the order or order item data, bookings won’t be exported automatically.

Exports remaining queued

If your exports freeze without completing, your site may be blocking HTTP requests in some way. Exports are processed asynchronously in the background, which requires your site to make requests to itself for information. As such, your site cannot block HTTP requests or exports will not start processing.

Here are some common causes of blocked requests:

• If your site is hosted with WordPress.com, the options table may be too limited. When setting up WooCommerce on WordPress.com, the site database must be updated; sometimes the options table limit is outdated at 64 characters when it should be 255 characters (as of WordPress 4.4). This limit should be fixed so that export jobs save properly. If WordPress.com confirms that the limit is 255 characters, please get in touch with our support team.
• Using a maintenance mode or blocking plugin. For example, the Airplane Mode plugin for developers will block HTTP requests.
• Your site is behind BasicAuth, which will require you to login before you can visit the site. This prevents background requests from completing. For example, WP Engine staging sites often use basic authentiacation to block site access. Click here to learn about correcting this issue, or disable BasicAuth while testing exports.
• Host files: For developers – hosts files to resolve a site to a different domain can’t be used with Customer/Order/Coupon Export and many other WooCommerce plugins. Customer/Order/Coupon Export uses wp_safe_remote_* requests to get data from itself, and these requests require a domain name. If your site is pointing to a domain from a hosts file, rather than a public site, these requests will fail.
• Your site host blocks requests from servers to themselves, called loopback connections. Click here to learn more about this requirement and how to test for this.

<a href="https://help.codibu.com/wp-content/uploads/2020/11/woocommerce-export-faq-basic-authentication.png"><img src="https://help.codibu.com/wp-content/uploads/2020/11/woocommerce-export-faq-basic-authentication.png?w=950" alt="Basic authentication sign in" width="950" height="620" class="aligncenter size-large wp-image-1900983" /></a>

Slow exports / out-of-memory errors

If your exports are slow or you’re encountering out-of-memory errors, please contact your host to confirm that the MySQLi extension is installed on your server and used by WordPress.

Customer / Order / Coupon Export defaults to streaming exports to their destination instead of sending an entire file to improve server efficiency and reduce the likelihood of out-of-memory errors with very large exports. This feature requires the MySQLi extension to be enabled and used by WordPress.

In rare cases, the extension is installed but not being used by WordPress. This can be remedied by adding define( 'WP_USE_EXT_MYSQL', false ); to your wp-config.php file.

SSH2 Extension is not installed, cannot connect via SFTP

If you see the error “Test failed: SSH2 Extension is not installed, cannot connect via SFTP” when trying to setup an automated SFTP export, you will need to reach out to your host to make sure the SSH2 extension is installed for PHP.

For those hosted with WordPress.com, this extension is not available, and unfortuantely SFTP exports will not be possible. You will need to use a different FTP type instead.

Other issues

Having difficulty with the plugin?

• Please ensure your site meets the plugin requirements.
• Check the FAQs to see if they address your question.
• Having trouble adding custom meta fields? Please ensure your meta keys are correct.
• Having a problem with an automated export delivery?
  • Confirm that your FTP, HTTP Post, or email information is correct.
  • Run a test to see if the transfer method is working properly.
  • Review our section on export schedules to see if there might be any issues with your export schedule.
  • If you encounter the following error when exporting via FTP – Error message: Uncaught Error: Call to undefined function ftp_connect() check phpinfo() to ensure that your server’s PHP has FTP support enabled.
• If you’re experiencing a different issue, please turn on and review error logs under WooCommerce > System Status > Logs and get in touch with support if this doesn’t help you identify the problem.

The post WooCommerce Customer / Order / Coupon Export first appeared on CODIBU.

WooCommerce Authorize.Net AIM integrates with Authorize.Net payment services to provide secure and powerful payment processing for your WooCommerce store. Accept credit cards and optionally accept eChecks on your WooCommerce store via Authorize.Net!

This plugin also supports Accept.js from Authorize.Net for improved security and decreased PCI compliance responsibility. When Accept.js is used, customer credit card information is no longer sent directly through your server and instead is handled directly by Authorize.Net, meeting the lower level PCI SAQ A-EP compliance level. You can learn more about Accept.js here.

Installation

1. Download the extension from your dashboard
2. Go to Plugins > Add New > Upload and select the ZIP file you just downloaded
3. Click Install Now, and then Activate
4. Go to WooCommerce > Settings > Checkout > Authorize.Net and read the next section to learn how to setup and configure the plugin.

Requirements

• An Authorize.Net account
• PHP 5.3+ (You can see this under WooCommerce > Status)

Setup and Configuration

Obtain Credentials from Authorize.Net

You need to have an active gateway account with Authorize.Net and follow the following steps to get your API credentials.

• • Go to Authorize.Net
  • Click on “Account Login” on the top-right
  • Enter your Login ID and Password then press Log In
  • From your home page, click on the Account Menu

• • In the left hand menu Account section click on “Settings”

• • In the Security Settings section click on “API Login and Transaction Key”

• • Your API Login ID will be displayed on this page, which will be copied and entered in the extension settings:

• • To create a new Transaction Key, answer the security question at the bottom of the page, check the “Disable Old transaction Key(s)” checkbox and press Submit.
  • Your new Transaction Key will be displayed on the next page – copy this transaction key, and enter it along with the API Login on the extension settings page:

If you would also like to enable Accept.js support, please see below for additional set up information.

Extension Settings

To configure the plugin, click on WooCommerce > Settings from the left hand menu, then the top tab “Checkout”. You should see Authorize.Net AIM as an option in the list at the top. Click this section to view the credit card settings.

• Enable / Disable – This will enable the gateway to be used by customers to checkout.
• Title – This is the text shown for the payment during checkout and on the Order Received page.
• Description – This is the text shown under the title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with test credit card numbers.
• Card Verification (CSC) – Enable this to require customers to enter their CVV / CV2 (Card Security Code) when checking out. This can be useful if you have requirements in your Authorize.Net account for CV2 verification.
• Transaction Type – This controls how transactions are submitted to Authorize.Net. You may choose either “Charge” or “Authorization”. If you select “Authorization”, you must manually capture and settle payments in your Authorize.Net control panel or on the WooCommerce orders screen after the transaction has been submitted. This defaults to “Charge”.
• Charge Virtual-Only Orders – (Shown if Transaction Type is set to “Authorization”) Enable this to force charges on order containing only virtual items so they’re captured immediately instead of authorized (for example, to grant download access right away)
  
• Capture Paid Orders – (Shown if Transaction Type is set to “Authorization”) Enable this to automatically attempt to capture transactions when orders change to a paid status.
• Accepted Cards – This controls the card logos that display during checkout. This is purely cosmetic and has no affect on the cards actually accepted by your merchant account.
• Detailed Decline Messages – Enable to display detailed messages to customers to provide reasoning for declines when possible instead of a generic error message.
• Debug Mode – Enable this is you are having issues correctly processing transactions. You can either log API requests / responses directly to the checkout / thank you page, save them to the WooCommerce Error Log (found under WooCommerce > System Status > Logs) or both. All debugging messages are cleaned of sensitive information before display, but as a best practice, please do not enable this unless you are having issues with the plugin.
• Environment – Switch between “Test” and “Production” credentials. Enable “Test” to send transactions to your Authorize.Net Test Account. Note: This is not the “test mode” that is listed under your Authorize.Net account. This is an entirely separate sandbox environment that requires a separate login. You can sign up for a test account here. Once you have done this, you can enter a separate API Login ID and API Transaction Key for your test account. Do not place your Test Account (or regular account) into “Test Mode” within the Authorize.Net control panel as transactions will not process at all if that mode is set.

Connection Settings

• Share connection settings – Enabling this will allow you to use connection / authentication settings between the credit card and eCheck gateways. If this is enabled, you’ll have to enter your Authorize.Net API Login ID and API Transaction Key under the eCheck settings.
• API Login ID – This is the API Login ID for your Authorize.Net account (Test or Production). Follow the steps above to get this.
• API Transaction Key – This is the API Transaction Key for your Authorize.Net account (Test or Production). Follow the steps above to get this.
• Accept.js – Enable this to use Accept.js to send card information directly to Authorize.Net and minimize PCI compliance scope.
• Client Key – If Accept.js is enabled, enter the Client Key generated for your account. Follow the instructions below to generate a client key.

eCheck Settings

To configure the eCheck settings, click on WooCommerce > Settings from the left hand menu, then the top tab “Checkout”. You should see Authorize.Net AIM eCheck as an option in the list at the top. Click this section to configure the eCheck gateway settings.

• Enabled – This will enable the eCheck gateway to be used by customers to checkout. IMPORTANT – You must have eChecks enabled on your Authorize.Net account for this to function correctly. Follow the process below under eCheck Issues to get eChecks setup and enabled.
• Title – This is the text shown for the eCheck gateway during checkout and on the Order Received page. This defaults to “eCheck”.
• Description – This is the text shown under the title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with a test bank account number.
• Environment – Switch between “Test” and “Production” credentials. Enable “Test” to send transactions to your Authorize.Net Test Account. Note: This is not the “test mode” that is listed under your account. This is an entirely separate sandbox environment that requires a separate login. You can sign up for a test account here. Once you have done this, you can enter a separate API Login ID and API Transaction Key for your test account. Do not place your Test Account (or regular account) into “Test Mode” within the Authorize.Net control panel as transactions will not process at all if that mode is set.
• Share connection settings – Enabling this will allow you to use connection/authentication settings between the credit card and eCheck gateways. If this is disabled, you’ll have to enter a new Authorize.Net API Login ID and API Transaction Key for eCheck transactions.
• Debug Mode – Enable this is you are having issues correctly processing transactions. You can either log API requests / responses directly to the checkout / thank you page, save them to the WooCommerce Error Log, or both. All debugging messages are cleaned of sensitive information before display, but as a best practice, please do not enable this unless you are having issues with the plugin..

Merchant Usage

It’s possible to use the WooCommerce Authorize.Net AIM extension with other gateways that support Authorize.Net emulation (such as eProcessing Network). You’ll need to enable the Authorize.Net Emulation gateway to use this. Read about how to enable and configure Authorize.Net emulation.

Capture Charges from WooCommerce Order Admin

Using version 3.0+ of the extension allows you to authorize charges during checkout, then manually capture them later. You can do this via your Authorize.Net control panel, or can easily do so from the WooCommerce Edit Order page.

You can read more about capturing charges with this plugin here.

Automatic Refund Support

Version 3.3.0 of Authorize.Net AIM adds automatic refund support for shops running WooCommerce 2.2+. This means that refunds can be processed directly in WooCommerce without the merchant logging into his or her Authorize.Net account.

You can read more about performing refunds with Authorize.Net AIM here.

Void Transaction Support

Transactions can be voided by using the same workflow as refunds. A void will occur if the transaction has been authorized, but not captured. In the case of Authorize.Net, voids will also occur for authorized & captured transactions that have not yet been settled. As funds haven’t been transferred, a refund can’t truly be processed.

Voided transactions must be voided in full; partial voids are not accepted by Authorize.Net. You can read more about voiding transactions here.

Authorize.Net Emulation

Please note that Authorize.Net Emulation does not support advanced features such as refunds, voids, and capturing charges from within WooCommerce. Only payment processing is supported.

To use Authorize.Net AIM with a gateway that supports Authorize.Net emulation, you need to enable the Authorize.Net emulator under Plugins > Installed Plugins — click “Enable emulation gateway”:

This allows you to use Authorize.Net’s emulation protocol for other gateways.

The Authorize.Net emulator settings will now be available under WooCommerce > Settings > Checkout. To use Authorize.Net emulation, you must enable the gateway and enter the Gateway URL and API credentials provided to you by your payment processor.

Extension Settings

• Enable / Disable – This will enable the gateway to be used by customers to checkout.
• Title – This is the text shown for the payment during checkout and on the Order Received page.
• Description – This is the text shown under the title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with test credit card numbers.
• Card Verification (CSC) – Enable this to require customers to enter their CVV / CV2 (Card Security Code) when checking out. This can be useful if you have requirements in your Authorize.Net account for CV2 verification.
• Transaction Type – This controls how transactions are submitted to Authorize.Net. You may choose either “Charge” or “Authorization”. If you select “Authorization”, you must manually capture and settle payments in your Authorize.Net control panel or on the WooCommerce orders screen after the transaction has been submitted. This defaults to “Charge”.
• Accepted Cards – This controls the card logos that display during checkout. This is purely cosmetic and has no affect on the cards actually accepted by your merchant account.
• Debug Mode – Enable this is you are having issues correctly processing transactions. You can either log API requests / responses directly to the checkout / thank you page, save them to the WooCommerce Error Log (found under WooCommerce > System Status > Logs) or both. All debugging messages are cleaned of sensitive information before display, but as a best practice, please do not enable this unless you are having issues with the plugin.
• Environment – Switch between “Test” and “Production” credentials. Enable “Test” to send transactions to your Authorize.Net Test Account. Note: This is not the “test mode” that is listed under your Authorize.Net account. This is an entirely separate sandbox environment that requires a separate login. You can sign up for a test account here. Once you have done this, you can enter a separate API Login ID and API Transaction Key for your test account. Do not place your Test Account (or regular account) into “Test Mode” within the Authorize.Net control panel as transactions will not process at all if that mode is set.
• Payment Gateway URL – The Gateway URL for the Authorize.Net gateway processor. Optionally, this URL can be changed to a different processor that allows Authorize.Net emulation.
• API Login – This is the API Login for your Authorize.Net account (Test or Production).  to get this. If you’re using this gateway for Authorize.Net emulation, then this will be the API Login provided to you by your payment processor.
• Transaction Key – This is the API Transaction Key for your Authorize.Net account (Test or Production).  to get this. If you’re using this gateway for Authorize.Net emulation, then this will be the API Transaction Key provided to you by your payment processor.

Other Information

eCheck Support

If you have enabled eChecks on your Authorize.Net account and within the plugin settings, customers will have the option to pay via Credit Card or eCheck. eCheck requires the customer to enter their bank routing number and bank account number. The billing first and last name entered during checkout is used as the Name on Account.

Accept.js Support

Version 3.9.0+ adds support for Accept.js from Authorize.Net. Accept.js improves security and decreases PCI compliance responsibility for merchants. To test or use Accept.js, you must have an SSL certificate installed on your site.

When Accept.js is enabled, customer credit card information is no longer sent directly through your server and instead is handled directly by Authorize.Net, meeting the lower level PCI SAQ A-EP compliance level.

You can learn more about Accept.js here. If you choose to enable Accept.js, you must generate a Client Key in your Authorize.Net account and enter this in the plugin settings.

To generate a client key, follow these steps:

1. Log into your Authorize.Net Account and go to Account > Settings.
2. Click on “Manage Public Key” in the “Security Settings” section.
   
3. If you already have generated a Client Key, you can copy it. If not, generate a new key by answering your security question and clicking “Submit” to generate the new key.
   
4. Copy your new Client Key and paste it into the plugin settings.

Once Accept.js is enabled, your credit card processing is now secured. The checkout process will appear unchanged for customers, but secured behind the scenes.

Enhanced Checkout Form

Authorize.Net AIM (v3.8.0+) supports an enhanced checkout form for all gateway modes. This improves both mobile and desktop checkout. You can read about the enhanced payment form here.

Detailed Decline Messages

When detailed decline messages are enabled, they will provide informative error messages to the customer at checkout when Authorize.Net returns a useful response. Detailed decline messages are supported by the AIM credit card and eCheck payment methods (not by the Emulation gateway).

You can read more about detailed decline messages here.

Apple Pay

Authorize.Net AIM contains a framework for Apple Pay, but Apple Pay can only be enabled by developers, as the certification process requires developer-only tools. If you work with a developer, please review the setup instructions and requirements here if you’d like to add Apple Pay to your store. Apple Pay support is not in the scope of plugin support, so we’re unable to assist with getting it enabled for your site.

Troubleshooting

If you’re using Accept.js, please note you may see a console error using Chrome developer tools at checkout:

XMLHttpRequest cannot load https://jstest.authorize.net/v1/AcceptCore.js. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://youstore.com' is therefore not allowed access.

This is expected by Authorize.Net and does not indicate a problem (transactions will process perfectly fine and are secure), annoying as it may be, which you can see here:

Right now I can tell you that the CORS warning “cannot load” is actually correct behaviour in that it’s alerting the fact that the page cannot call our core js library only the Accept.js library. So that will not impact functionality (we are nonetheless looking at ways to stop the browser doing this).

Authorize.Net Error Codes

Having a different trouble? First, please refer to the Authorize.Net Response Code Reference — enter the error code you see into this tool to view the source of the error. In some cases, such as a transaction being held for review or being declined, the plugin cannot change the issue and it must be resolved in your Authorize.Net account.

Notes
Orders with Response Code = 4 will be approved, but can be cancelled manually in the WooCommerce admin and Authorize.Net Merchant Area area later if they fail review.

Be sure to have “Partial Authorization” turned off in your Authorize.Net Merchant Area. This will restrict orders with with Response Code = 4 and Response Code = 295 from being approved. “Allow Partial Payments” is off by default, but to verify it is off, follow these steps:

• Login to your Authorize.Net Merchant Area
• Press “Account” in the top toolbar
• Under the “Transaction Format Settings” area click on “Partial Authorization”
• Verify “Allow Partial Payments” is not checked

Required Field Errors

If you receive an error like (E00027) - The transaction was unsuccessful. Error Code: 33 - [Field Name] is required., your Authorize.Net account is likely setup to require a field that our plugin cannot send. These errors can occur on orders, refunds, and void transactions.

To resolve this issue, you should remove all field requirements from your Authorize.Net account by following the steps below:

1. Login to your Authorize.Net Account.
2. Go to Account > Payment Form > Form Fields.
3. Uncheck the Required boxes for all fields.
4. Click Submit.

eCheck Issues

Make sure the ‘WEB’ eCheck type is enabled on your Authorize.Net account, or you might see errors like [Code 246] - This eCheck.Net type is not allowed. To get this setup, follow these steps:

1. Set up an eTicket and ask for the ‘WEB’ eCheck type to be enabled (be sure you are an account owner and know your gateway ID).
2. WEB transactions are usually enabled within 2 business days, but there is a funding hold automatically placed on your account — you can take funds in, but not get them out, until you pass another security check with the underwriting department.
3. To expedite the process, call them on the phone and they will check out your website while on the line with you. They will look to make sure you have a valid SSL on cart/checkout, and prominently placed terms of use and privacy policy pages.
4. Once you meet those requirements, the funding hold should be removed.

Refund Issues

You may see an error message that looks something like this when trying to process an automatic refund:

Oops, you cannot partially void this order. Please use the full order amount.

This means that you’re trying to perform a partial refund, but the charge has not been settled (typically when you try to refund within a day of the purchase). The plugin tries to void this order since the funds have not been transferred (to cancel the order instead of refunding it), but Authorize.Net does not permit partial voids.

Please wait until the charge has settled (about one day after the charge was made) to refund this transaction.

Authorize.Net Test Credentials

Authorize.Net production credentials cannot be used in test mode. To test the plugin, merchants sometimes put their production accounts into the “Test modes” from their Authorize.Net accounts, which returns dummy data for live transactions. However, this will not work with the plugin’s test mode either, as these are still production credentials.

To use the plugin in test mode, you should get a set of dedicated test credentials from Authorize.Net. These work with the test mode in the plugin. Your production Authorize.Net credentials should always be live, and never set to test mode.

Frequently Asked Questions

Q: Isn’t the AIM API deprecated? Will your plugin still work?
A: Despite the similarity in the name, our Authorize.Net AIM plugin doesn’t use the AIM API. We use the recommended Authorize.Net API, so there’s no need to be concerned about the AIM API being deprecated.

Q: Can I accept subscriptions for Authorize.Net using ARB with the AIM extension?
A: At this time, accepting subscriptions using ARB with Authorize.Net AIM is not possible. Implementing ARB support is not optimal, as notifications for failed subscription payments are not reliable and this issue could cause significant problems for stores using this method. We recommend that you check out the Authorize.Net CIM extension for Subscriptions support instead.

Q: Can I process automatic refunds with eChecks or Emulation?
A: Unfortunately this is not possible with eChecks or with Authorize.Net Emulation. Refunds can automatically be processed from WooCommerce with a credit card purchase via AIM, but not for an eCheck purchase.

Q: My customers get email receipts from WooCommerce and Authorize.Net. How do I get rid of Authorize.Net receipts?
A: The plugin cannot disable these for you, but you can disable these emails in your Authorize.Net account — click here for instructions.

Q: How do I capture a higher amount than what is authorized (like a restaurant)?
A: Authorize.Net (along with most any eCommerce payment processors) cannot do this with card-not-present transactions (which is what online payments are). Captures can only be up to the value of what’s authorized: “As soon as the product is shipped, the merchant can capture an amount up to the amount of the authorization.”

When gas stations and restaurants do this, they’re using a particular POS system that gives them a certification to capture a certain percentage over the authorized amount. This isn’t available with eCommerce systems to be able to capture amounts higher than what’s authorized, so this is not possible on your WooCommerce site.

Q: Authorize.Net supports Apple Pay for web payments. Can I use this in my store?
A: This plugin does not support Apple Pay by default, as the set up process to use Apple Pay with Authorize.Net is not possible for most merchants to complete independently. If you work with a developer, please review the setup tips and requirements here, as the plugin does have tools developers can use to enable Apple Pay.

The post WooCommerce Authorize.Net AIM first appeared on CODIBU.

WooCommerce Authorize.Net Gateway integrates with Authorize.Net payment services to provide secure and powerful payment processing for your store. With this gateway, you can accept credit cards and eChecks and let customers save their payment details to your site for fast and easy checkouts. This payment gateway includes full support for WooCommerce Subscriptions and WooCommerce Pre-Orders!

This plugin also includes Accept.js from Authorize.Net for improved security and decreased PCI compliance responsibility. Customer credit card information is handled directly by Authorize.Net to offload some security concerns. Click here to learn more about Accept.js

Requirements

• An Authorize.Net account
• PHP 5.6+ (You can see this under WooCommerce > Status)
• An SSL certificate. An SSL certificate is also required on local test environments.

Installation

1. Ensure your store meets the plugin requirements.
2. Download the extension from your WooCommerce dashboard.
3. Go to Plugins > Add New > Upload and select the ZIP file you just downloaded.
4. Click Install Now and then Activate.
5. Click Configure and read the next section to learn how to setup the plugin.

Getting Started

 

To begin using Authorize.Net, you must first connect the plugin to your Authorize.Net account. Follow the steps below to find your API credentials on Authorize.Net and setup the plugin:

1. 1. Login to your Authorize.Net account.
   2. Go to Accounts > Settings > API Credentials & Keys.

1. 1. Copy your API Login ID.
   2. Select the New Transaction Key radio button and click Submit. Copy the Transaction Key.
   3. If you want to setup webhooks, select the New Signature Key radio button and click Submit to generate the Signature Key.

1. Now, log into your site and go to WooCommerce > Settings > Payments and select WooCommerce Authorize.Net.
2. Paste the API Login ID, API Transaction Key, and API Signature Key, if applicable.
3. Click Save Changes.

That’s it! You are now ready to start accepting credit cards via Authorize.Net! Keep reading if you want to tweak settings and customize the checkout process.

Credit Card Settings

You can configure the following settings for the Authorize.Net credit card gateway:

• Enable / Disable: Allow customers to use this gateway to checkout.
• Title: The text shown for the payment during checkout and on the Order Received page.
• Description: The text shown under the gateway’s title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with test credit card numbers.
• Card Verification (CSC): Require customers to enter their card security codes when checking out. This can be useful if you have requirements in your Authorize.Net account for CV2 verification.
• Transaction Type: Controls how transactions are submitted to Authorize.Net. Select “Charge” to automatically capture payments. If you select “Authorization”, you must manually capture and settle payments in your Authorize.Net control panel or on the WooCommerce orders screen after the transaction has been submitted. This defaults to “Charge”.
• Charge Virtual-Only Orders: If Transaction Type is set to “Authorization”, enable this to automatically capture charges for orders with only virtual products. For downloadable products, this will grant downloads access right away.
• Capture Paid Orders: If Transaction Type is set to “Authorization”, enable this to automatically capture charges when orders move to a paid status.
• Accepted Cards: Determines which card logos are displayed during checkout. This has no impact on which cards are accepted by your merchant account.
• Tokenization: Let customers save their payment methods for future use at checkout. This is required for Subscriptions or Pre-Orders.
• Detailed Decline Messages: Display detailed messages to customers to provide reasoning for declines instead of a generic error message when possible. Click here to read more about detailed decline messages.
• Debug Mode: Enable when you’re having issues processing transactions. You can choose to log API requests directly on the checkout page, save them to the WooCommerce > Status > Logs page, or both. As a best practice, please do not enable this setting unless you’re having issues with the plugin.
• Environment: Switch between “Test” and “Production” credentials. Enable “Test” to send transactions to your Authorize.Net Test Account. Note: This is not the “test mode” that is listed under your account. This is an entirely separate sandbox environment that requires a separate login and separate API credentials. Do not place your Test Account (or regular account) into “Test Mode” within the Authorize.Net control panel as transactions will not process at all if that mode is set.
• Share connection settings: If using the credit card and eCheck gateways, select this setting to share credentials between the gateways so you don’t have to enter them twice.
• API Login ID: Follow the steps above to retrieve your API Login ID.
• API Transaction Key: Follow the steps above to generate your API Transaction Key.
• API Signature Key: Optional. Only required if you want to enable webhooks for Authorize.Net account updates. Follow the steps above to generate your API Signature Key.
• Payment Form Type: You can choose how you’d like to display the payment form. The Inline option meets SAQ-A EP PCI requirements while the Lightbox option supports SAQ A standards.

eCheck Settings

You can configure the following settings for the Authorize.Net eCheck gateway:

• Enable / Disable: Allow customers to use this gateway to checkout. You must enable eChecks on your Authorize.Net account to use the eCheck gateway. Follow the process below under eCheck Issues to get eChecks setup and enabled.
• Title: The text shown for the payment during checkout and on the Order Received page.
• Description: The text shown under the gateway’s title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with a test bank account number.
• Tokenization: Let customers save their payment methods for future use at checkout. This is required for Subscriptions or Pre-Orders.
• Authorization: Display an authorization message during the checkout process.
• Authorization Message: If Authorization is enabled, enter the message you want to show to your customers. You can use the following merge tags:
  • {merchant_name}: Your store name
  • {order_date}: Date of purchase
  • {order_total}: Total order value
• Recurring Authorization Message: If Authorization is enabled and WooCommerce Subscriptions is active on your site, you can enter the message you want to show your customers for recurring payments.
• Detailed Decline Messages: Display detailed messages to customers to provide reasoning for declines instead of a generic error message when possible. Click here to read more about detailed decline messages.
• Debug Mode: Enable when you’re having issues processing transactions. You can choose to log API requests directly on the checkout page, save them to the WooCommerce > Status > Logs page, or both. As a best practice, please do not enable this setting unless you’re having issues with the plugin.
• Environment: Switch between “Test” and “Production” credentials. Enable “Test” to send transactions to your Authorize.Net Test Account. Note: This is not the “test mode” that is listed under your account. This is an entirely separate sandbox environment that requires a separate login and separate API credentials. Do not place your Test Account (or regular account) into “Test Mode” within the Authorize.Net control panel as transactions will not process at all if that mode is set.
• Share connection settings: If using the credit card and eCheck gateways, select this setting to share credentials between the gateways so you don’t have to enter them twice.
• API Login ID: Follow the steps above to retrieve your API Login ID.
• API Transaction Key: Follow the steps above to generate your API Transaction Key.
• API Signature Key: Optional. Only required if you want to enable webhooks for Authorize.Net account updates. Follow the steps above to generate your API Signature Key.
• Payment Form Type: Choose to display the payment form inline or in a lightbox. Select “Inline” to support PCI-DSS SAQ A-EP compliance.

eCheck Setup with Authorize.Net

To enable eCheck processing on your Authorize.Net account:

1. Setup an eTicket and ask for the “WEB” eCheck type to be enabled. Be sure you are an account owner and know your gateway ID.
2. WEB transactions are usually enabled within 2 business days, but there is a funding hold automatically placed on your account – you can take funds in, but can’t take them out until you pass another security check with the underwriting department.
3. To expedite this process, call the Authorize.Net underwriting department so they can check your website while on the phone with you. They’ll ensure you have a valid SSL on cart/checkout and prominently placed terms of use and privacy policy pages.
4. Once you’ve met these requirements, the funding hold will be removed.

Webhook Setup

Webhooks notify your WooCommerce site when customer profiles and payment profiles are deleted from your Authorize.Net account. This is helpful when using WooCommerce Subscriptions to ensure that payment token removals are logged on your site for troubleshooting purposes.

Follow the steps above to generate your API Signature Key, which you can enter in the plugin settings to enable webhooks. Then, click the link in the settings notice to enable webhooks. This will push the required information into your Authorize.Net account.

Authorize.Net will now notify your site when the customer or payment profiles are deleted from your account. We do, however, recommend avoiding changes within your account when possible.

Managing Orders

As a site administrator, you can use the WooCommerce Authorize.Net gateway to manually capture charges and automatically refund/void transactions as needed.

Capture Charges

If you are using version 2.0+ of the Authorize.Net gateway and the Transaction Type setting is set to “Authorization”, you can manually capture these payments from the WooCommerce Orders page. Click here to read more about capturing charges.

Automatic Refunds

If you are using version 2.0+ of the Authorize.Net gateway and version 2.2+ of WooCommerce, you can process refunds directly in WooCommerce without needing to log into your Authorize.Net account. Click here to read more about issuing automatic refunds from WooCommerce.

Void Transactions

You can void transactions directly in WooCommerce in the following circumstances:

• If your Transaction Type setting is set to “Authorization”, you can void when the transaction has been authorized but not yet captured.
• If your Transaction Type setting is set to “Charge”, you can void when the transaction has not yet been settled (e.g. funds haven’t been transferred from the customer’s account to your Authorize.Net account).

Authorize.Net does not accept partial voids. If a transaction is no longer eligible to be voided, you must refund the order. Click here to read more about voiding transactions in WooCommerce.

Gateway Features

Your customers can take advantage of the following features when your site uses WooCommerce Authorize.Net.

Saving Payment Methods

 

Customers can save payment methods during the checkout process or from their My Account area. This lets them quickly select payment details during future checkouts and also lets your site support Subscriptions and Pre-Orders.

To manage their saved payment methods, customers can go to My Account > My Payment Methods. From here, they can add new payment methods (credit cards or eChecks), set their default method, and delete any old or expired methods. Click here to read more about managing saved payment methods.

Subscriptions / Pre-Orders Support

 

 

 

WooCommerce Authorize.Net supports all features of WooCommerce Subscriptions and WooCommerce Pre-Orders for both credit cards and eChecks (if enabled).

Accept.js

Version 3.0+ of WooCommerce Authorize.Net includes automated support for Accept.js. Once you have configured the gateway, we can retrieve the information required to use Accept.js from your Authorize.Net account – no extra configuration steps required!

This feature means that customer payment information is handled directly by Authorize.Net, meeting the lower level PCI SAQ A-EP compliance level. Accept.js is handled behind the scenes, so your customers won’t notice any change to their checkout process. Click here to learn more about Accept.js.

Enhanced Checkout Form

Authorize.Net supports an enhanced checkout form that improves the checkout experience on mobile and desktop devices. Click here to read about the enhanced payment form.

Authorize.Net Emulation

Please note that Authorize.Net Emulation does not support advanced features such as refunds, voids, and capturing charges from within WooCommerce. Only payment processing is supported.

To use Authorize.Net with a gateway that supports Authorize.Net emulation, you need to enable the Authorize.Net emulator under Plugins > Installed Plugins — click “Enable emulation gateway”:

This allows you to use Authorize.Net’s emulation protocol for other gateways.

The Authorize.Net emulator settings will now be available under WooCommerce > Settings > Payments. To use Authorize.Net emulation, you must enable the gateway and enter the Gateway URL and API credentials provided to you by your payment processor.

Extension Settings

• Enable / Disable – This will enable the gateway to be used by customers to checkout.
• Title – This is the text shown for the payment during checkout and on the Order Received page.
• Description – This is the text shown under the title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with test credit card numbers.
• Card Verification (CSC) – Enable this to require customers to enter their CVV / CV2 (Card Security Code) when checking out. This can be useful if you have requirements in your Authorize.Net account for CV2 verification.
• Transaction Type – This controls how transactions are submitted to Authorize.Net. You may choose either “Charge” or “Authorization”. If you select “Authorization”, you must manually capture and settle payments in your Authorize.Net control panel or on the WooCommerce orders screen after the transaction has been submitted. This defaults to “Charge”.
• Accepted Card Logos – This controls the card logos that display during checkout. This is purely cosmetic and has no affect on the cards actually accepted by your merchant account.
• Debug Mode – Enable this is you are having issues correctly processing transactions. You can either log API requests / responses directly to the checkout / thank you page, save them to the WooCommerce Error Log (found under WooCommerce > System Status > Logs) or both. All debugging messages are cleaned of sensitive information before display, but as a best practice, please do not enable this unless you are having issues with the plugin.
• Environment – Switch between “Test” and “Production” credentials. Enable “Test” to send transactions to your Authorize.Net Test Account. Note: This is not the “test mode” that is listed under your Authorize.Net account. This is an entirely separate sandbox environment that requires a separate login. You can sign up for a test account here. Once you have done this, you can enter a separate API Login ID and API Transaction Key for your test account. Do not place your Test Account (or regular account) into “Test Mode” within the Authorize.Net control panel as transactions will not process at all if that mode is set.
• Payment Gateway URL – The Gateway URL for the Authorize.Net gateway processor. Optionally, this URL can be changed to a different processor that allows Authorize.Net emulation.
• API Login ID – This is the API Login for your Authorize.Net account (Test or Production). Follow the steps above to get this. If you’re using this gateway for Authorize.Net emulation, then this will be the API Login provided to you by your payment processor.
• API Transaction Key – This is the API Transaction Key for your Authorize.Net account (Test or Production). Follow the steps above to get this. If you’re using this gateway for Authorize.Net emulation, then this will be the API Transaction Key provided to you by your payment processor.

Frequently Asked Questions

Q: Why am I receiving an error message on subscription renewals saying that Card Code is required? It’s not required in my plugin settings!
A: If you’re seeing an error like “Authorize.Net Payment Failed (3 E00027): Card Code is Required…”, it’s likely that Card Code is required on your Authorize.Net account. For PCI compliance and security reasons, Authorize.Net cannot store CSCs for subscription renewals, so card codes are unavailable for renewal orders. If your Authorize.Net account requires these, the orders will fail. Click here to learn how to disable this requirement.

Q: Why don’t Subscriptions display inside the Authorize.Net control panel?
A: Subscriptions aren’t shown in Authorize.Net because the gateway doesn’t use ARB (automated recurring billing). It tokenizes the customer’s payment method and then the Subscriptions plugin handles charging the payment method. This is far more flexible than ARB and thus supports a lot of features, such as changing payment dates and amounts, that ARB can’t handle.

Q: Why did I receive a “test transaction successful” email?
A: During checkout, the extension validates the payment information entered by the customer (i.e. confirms that the card number, expiration date, etc. are correct). This “test transaction” does not charge the customer, but generates an email to the merchant. You can email support@authorize.net to have them disable this email notification to you.

Q: Can I process automatic refunds with eChecks?
A: No – automatic refunds from WooCommerce can only be processed for credit card transactions.

Q: I’m migrating sites – can I import customer IDs and payment profile IDs to my new site?
A: The Authorize.Net plugin stores the customer ID, payment profile ID, and shipping profile ID as meta fields, so you could use an export plugin like Customer/Order CSV Export to pull down the IDs from your old site and use an import plugin like Customer/Order/Coupon CSV Import Suite to import these IDs to you new site! Other export/import plugins might work well here, too, so long as they are capable of exporting and importing customer/user meta.

Q: My customers get email receipts from WooCommerce and Authorize.Net. How do I get rid of Authorize.Net receipts?
A: You can disable these emails in your Authorize.Net account. Click here for instructions on disabling customer email receipts.

Q: How do I capture a higher amount than what is authorized (like a gas station or restaurant)?
A: Authorize.Net (along with most any eCommerce payment processor) cannot do this with card-not-present transactions, such as online payments. For these payments, you can only capture up to the value of the authorization: “The amount being requested for capture is less than or equal to the original authorized amount.”

When gas stations and restaurants do this, they’re using a particular POS system that gives them a certification to capture a certain percentage over the authorized amount. This functionality isn’t available for eCommerce systems, so this isn’t possible on your WooCommerce site or with the Authorize.Net plugin.

Q: Authorize.Net supports Apple Pay for web payments. Can I use this in my store?
A: Authorize.Net CIM contains a framework for Apple Pay, but it can only be enabled by developers, as the certification process requires developer-only tools. If you work with a developer and would like to add Apple Pay to your store, please click here to review the setup instructions and requirements. Please note that configuring Apple Pay support for this plugin is considered a customization and is not covered by our support policy.

Q: Does this plugin support 3D Secure? I need to meet Strong Customer Authentication (SCA) requirements.
A: WooCommerce Authorize.Net does not support 3D Secure at this time — Authorize.Net’s API does not support accepting the customer data required to meet 3D Secure v2.0 requirements (which is required for folks seeking to comply with PDS2 regulations / SCA requirements). If you need to enable SCA, please ask your Authorize.Net representative about migrating you to CyberSource. You can read more about PSD2 and Authorize.Net here, and see updates on 3D Secure with WooCommerce CyberSource here.

Q: I have a local test environment, do I need to have an SSL certificate installed?
A: Yes, an SSL certificate is also required on local test environments. In order to obtain an SSL Certificate for your local site, you can generate a self-signed certificate, or install a test certificate with a service such as the free Let’s Encrypt.

Troubleshooting

Authorize.Net Test Credentials

To run tests with this plugin, you will need a set of dedicated test credentials from Authorize.Net. Your live credentials cannot be used in “Test” mode. When you change the Environment setting to “Test”, the Connection Settings fields will remove your live credentials and let you enter your test credentials. When you switch back to “Production”, the plugin will restore your live credentials.

Authorize.Net Error Codes

Authorize.Net provides many different error/response codes that can provide helpful information about what caused an error during payment processing. Click here to review Authorize.Net’s Response Code Reference. You can enter the code in this reference tool to see the cause of the error. In some cases, such as a transaction being held for review or declined, the plugin can’t resolve the issue. In those cases, you must fix the problem from your Authorize.Net account.

Notes:

• Orders with Response Code = 4 will be approved, but can be cancelled manually in the WooCommerce admin and Authorize.Net Merchant Area area later if they fail review.
• Be sure to have “Partial Authorization” turned off in your Authorize.Net Merchant Area. This will restrict orders with with Response Code = 4 and Response Code = 295 from being approved. “Allow Partial Payments” is off by default, but to verify it is off, follow these steps:
  • Login to your Authorize.Net merchant area.
  • Go to Account > Partial Authorization.
  • Ensure that Allow Partial Payments is unchecked and click Submit to save your changes, if applicable.

Required Field Errors

If you receive an error like (E00027) - The transaction was unsuccessful. Error Code: 33 - [Field Name] is required., your Authorize.Net account is likely setup to require a field that our plugin cannot send. These errors can occur on orders, refunds, and void transactions.

To resolve this issue, you should remove all field requirements from your Authorize.Net account by following the steps below:

1. Login to your Authorize.Net Account.
2. Go to Account > Payment Form > Form Fields.
3. Uncheck the Required boxes for all fields.
4. Click Submit.

Accept.js Errors

If you receive an error like Accept.js Error: payment nonce is missing, your checkout page is likely not loading the Accept.js file when our plugin expects it to. This is usually caused by a JavaScript conflict of some kind, typically with your theme or another plugin. Often times, optimization plugins interfere with how JavaScript loads on your checkout page and cause this error. A few conflicting plugins to look for are:

• Autoptimize
• SG Optimizer
• Hummingbird Pro

If you are using one of these plugins, disabling the plugin completely or adjusting its settings so they don’t optimize your checkout page should resolve the error.

eCheck Issues

If you enabled eChecks in the Authorize.Net gateway plugin but have not enabled WEB eCheck enabled on your Authorize.Net account, you may see errors like [Code 246] - This eCheck.Net type is not allowed. Click here for instructions on setting up eChecks on your Authorize.Net account.

Refund Issues

When attempting to process an automatic refund, you may see the following error message:

Oops, you cannot partially void this order. Please use the full order amount.

This means that you’re trying to perform a partial refund, but the charge hasn’t been settled yet. This can happen when you try to refund within a day of purchase. The Authorize.Net plugin tries to void this order, since the funds haven’t been transferred yet, but Authorize.Net doesn’t permit partial voids.

To resolve this, please wait until the charge has settled (about 24 hours after the order was charged) before trying the refund again.

Failed Subscription Renewals

The most frequent cause of failed subscription renewals is the “Payment token is missing or invalid” error. This occurs when payment data has changed on your site or within Authorize.Net for this user, but the subscription record hasn’t been updated.

For a renewal to process successfully, a few conditions must be met:

• The customer must have a payment token on your site. Click here for information on viewing user payment tokens.
• The payment token data in the user profile must match data on the subscription record. Click here to learn more about finding this information in the subscription record.
• The payment must be accepted by Authorize.Net. Our plugin has no control over declined transactions.

If the customer profile ID and payment profile ID (payment token) don’t match between the user and subscription records, any automated renewal orders will fail until you update the subscription record IDs to match the user record IDs.

We have a few recommendations for preventing mismatches between user and subscription records:

• Don’t use the same Authorize.Net API credentials on multiple sites. If customer payment information is changed on one site but not another site, your payment profile information may no longer sync with your Authorize.Net account properly.
• If you take customer information over the phone, be sure to update the payment information on your site instead of on Authorize.Net. Our plugin will push changes from your site to your Authorize.Net account, but won’t be notified of payment information changes in Authorize.Net, so it can’t update your site’s subscription records.
• If you make any changes to customer or payment profile information from your Authorize.Net account, be sure to also update the subscription records on your site. You should double-check customer profile ID and payment profile ID for the subscription any time you make changes in Authorize.Net.
• If your customers want to update a subscription payment method, they must use the subscription “Change Payment” process. Simply adding a new payment method to their site account won’t change the subscription’s payment method. If you’re doing this for them, we recommend using the free User Switching plugin to impersonate their account.

Other Issues

Having a different problem? Follow these steps to make sure everything is setup correctly before posting a support request:

• Please ensure that your site meets the plugin requirements.
• Check the FAQs to see if they address your question.
• Confirm that your API Login ID and API Transaction Key are correct.
• Enable Debug Mode and review the errors codes/messages provided by Authorize.Net. Click here to learn more about Authorize.Net error/response codes. In some cases, such as a transaction being held for review or declined, the plugin cannot change the issue and it must be resolved in your Authorize.Net account. If the error code indicates an issue with the plugin, please submit a support ticket and include the logs to help us troubleshoot.

Upgrading from another plugin

If you’re upgrading from a legacy WooCommerce.com integration (Authorize.Net AIM, DPM, or SIM / Accept Hosted), you will see a notice in that plugin to migrate to this integration. Your existing plugin subscription has automatically been converted to a subscription for the new and improved Authorize.Net integration! You can migrate your site to this integration seamlessly with a couple of clicks.

You should be connected to WooCommerce.com to complete this migration. If your site has not been connected to WooCommerce.com, you will be prompted to connect first. (Check out this document for help, or see our FAQs below if you can’t connect.)

Once connected to WooCommerce.com, you’ll see a notice to migrate to this version of the plugin when you’re ready.

With a single click, this will automatically take care of the full migration:

• The unified plugin (this new integration) will be downloaded from your WooCommerce.com account and installed.
• This plugin will be activated.
• Your settings, such as your Authorize.Net credentials, will be migrated over to the new plugin automatically.
• Payments will continue to process seamlessly, as will refunds, charge captures, and more.

Upgrade FAQs

Q: What if I’m unable to connect to WooCommerce.com? (For example, if your site sells CBD oil products.)
A: You can still migrate! You’ll need a couple more steps, though:

1. Download the new Authorize.Net integration from your WooCommerce.com account (you will already have a new subscription for it).
2. Install this plugin under Plugins > Add New > Upload.
3. Activate this plugin.

Once this new, unified plugin is activated, it will handle migrating your settings automatically for you.

Q: Why were the AIM / CIM / DPM / SIM plugins replaced with this one?
A: When we originally built all of the various Authorize.Net integrations for WooCommerce, it was because Authorize.Net had several different payment processing products. This is no longer the case anymore, so it was confusing to have to choose the right plugin. Since Authorize.Net’s offerings have become more streamlined, we needed to migrate all WooCommerce stores to use this version of the plugin, which supports the latest and greatest offerings from Authorize.Net.

Q: What has changed from my previous plugin?
A: You’ve gained some new features!  “Which features” depends on what plugin you were using previously. However, all Authorize.Net users now have the ability to let customers save payment methods, use WooCommerce Subscriptions, use WooCommerce Pre-orders, and more. You can also choose to keep your checkout form inline (helping you meet SAQ A-EP PCI compliance standards) or use a lightbox checkout form (helping you meet SAQ A PCI compliance standards).

Q: What will happen to my plugin subscription?
A: Your WooCommerce.com account was automatically gifted a new subscription for this plugin. Here’s how we handled the change:

• You have been gifted a subscription for the new plugin that ends on the same date as your original plugin subscription.
• If your plugin subscription was set to auto-renew, we’ve turned it off, and enabled auto-renew on the new plugin subscription. If your subscription did not auto-renew, we’ve left it disabled.
• Your previous plugin subscription is still in your account for now, but it will end on its original date, and cannot be renewed again (as the legacy plugins are now retired).

Q: What if the migration doesn’t go smoothly?
A: The worst-case scenario is that we’re not able to migrate the plugin’s settings, and you would need to update them manually. This is a pretty foolproof process, though. If you’d like to double-check the migration, we recommend completing it at an off-peak time, then double-checking a test payment with your store. Our support team is also happy to help out with any questions or migration concerns!

For Developers

Here are a couple of example snippets for some of the Authorize.Net CIM filters in place:

Default the “Securely Save to Account?” checkbox on the payment form to checked

Adjust authorize-only transaction order status from “On hold” to something else

The post WooCommerce Authorize.net first appeared on CODIBU.

UPS can calculate quotes for both domestic and international parcels.

Installation

1. Download the extension from your WooCommerce dashboard.
2. Go to Plugins > Add New > Upload and select the ZIP file you just downloaded.
3. Click Install Now, and then Activate.

More information at: Installing and Managing Plugins.

API & Debug 

Go to: WooCommerce > Settings > Shipping > UPS.

1. UPS User ID – Get your UPS User ID from the developer site by signing up at UPS Developer Kit.
2. UPS Password – Set by you during signup.
3. UPS Access Key – Sent to you after signup.
4. UPS Account Number – Sent to you after signup.
5. Customer Classification – Determines what rates are returned. Note that Retail Rates will match the online calculator.
6. Debug Mode – Enable/disable debug mode to show debugging information on your cart/checkout.
7. Save changes.

Configuration

1. Go to: WooCommerce > Settings > Shipping.
2. Select your Shipping Zone that you want to add the method to, and press the Add shipping method + button on the right
   
3. Select UPS from the dropdown and press Add shipping method:
   
4. Configure the settings:
   • Method & Origin Settings
     1. Method Title – Name the shipping method. This is visible to customers.
     2. Origin City – Enter city you are sending from.
     3. Origin Postcode – Set to the postcode from where you ship. It is sent to the UPS API.
     4. Origin Country – Set to the country from where you ship. It is sent to the UPS API.
   • Services and Packaging
     1. Services – Choose to rename and/or rearrange the order of UPS shipping rates.
     2. Offer Rates – Select whether to display all rates available or only the cheapest.
     3. Negotiated Rates – Enable negotiated rates or not. More at: Account-Specific Negotiated Rates. This must be approved by UPS, or the API returns an error. It is sent to the UPS API.
     4. Delivery Confirmation – Optionally you may charge customers for delivery confirmation. This just adds the specified amount to the returned rates.
     5. Parcel Packing Method – See below.
     6. UPS Packaging – You can select from a built-in list of standard UPS packaging to use.
     7. Custom Boxes – Here you can add custom box sizes to pack into.
   • Advanced Options
     1. Origin Address – Sometimes you may need to enter the address for the sender/origin.
     2. Residential – Choose whether to indicate deliveries as residential or commercial addresses.
        * Users are permitted to enter PO Boxes as a shipping address, even though UPS does not allow it.
     3. Insured value – Request Insurance to be included in UPS rates.
     4. Fallback – Enter a fallback amount for shipping, if no rates are found.
     5. Weight/Dimension Units – Only change this if you’re getting the “This measurement system is not valid for the selected country method.”

Parcel Packing Methods

There are two packing methods with UPS, and each affects the parcels you send to the API.

Pack items individually (Default)

Each item in your cart (non-virtual) is sent to the UPS API. Quotes for all items are combined to calculate the final cost. Only the weight is required, but also entering product dimensions produces a more accurate quote. For even more accuracy, we recommend the box packer method.

To use this method, add a new product then scroll down to Product Data > Shipping to enter the product dimensions.

Pack into boxes with weights and dimensions (Recommended)

Using this method, you create your own custom box sizes in UPS Settings. The extension uses the weight/dimensions of products added to the cart, filling the custom box size from smallest to largest based on volume and size, then sends the number of boxes/size to the UPS API for a shipping estimate. Both product weight and dimensions are needed for this option to accurately calculate what boxes are needed.

Selecting this option you must follow the steps listed below for UPS Packaging or Custom Box Packing for this method to work.

UPS Packaging

UPS offers standard boxes for shipping. UPS Packaging:

Start typing the package you want to include, and it auto-populates the field for you.

Custom Box-Packing

The box packer included with this shipping method groups items into boxes that you define by height, width, length, weight, and max-weight. The packing is mainly volume based, but also considers item sizes.

Setting up box sizes

1. Go to: WooCommerce > Settings > Shipping.
2. Select your Shipping Zone containing UPS, then click UPS
3. Scroll down to Custom Boxes and select Add Box to set up box dimensions:

Outer dimensions are used for parcel dimensions and are passed to the API.

Inner dimensions are used for packing, and items should fit within these.

Box weight is the weight of the actual box, and is added to the weight of contents.

Max weight is the maximum weight your box can hold. This includes contents weight and box weight.

How the calculation works

The packer:

1. Finds boxes that fit items being packed (uses H x W x D).
2. Packs all fitting items into boxes (using volume).
3. Uses the smallest box that fits 100% of items *or* uses the highest % packed box, and then passes unpacked items back and repeats the process.
4. Packs unpackable items alone, using item dimensions.
5. Returns all packed boxes.

Handling Fees

To add handling fees to shipping calculations, you can use a Price Adjustment column in the Services section. Each UPS service can be increased or decreased (by adding the “-” sign) separately, using price adjustment columns in the row.

Use the Price Adjustment ($) column to add a flat amount to the shipping quote. In this example, the 3-Day Select and Ground shipping methods are increased by $3.50.

Use the Price Adjustment (%) to increase the shipping quote by a percentage. In this example, the 3-Day Select and Ground shipping methods are increased by 1% of the quote returned by UPS.

Customer Usage

Customers get quotes, after inputting their address, from two places:

• Cart page – via the shipping calculator
• Checkout page – via the shipping and billing forms

Available Shipping Services for UPS Extension

These services are included with the UPS Shipping extension:

Domestic

3-Day Select
Ground
2nd Day Air
2nd Day Air AM
Next Day Air
Next Day Air Saver
Next Day Air Early AM

International

Standard
Worldwide Express
Worldwide Express Plus
Worldwide Expedited Standard
Worldwide Saver

FAQ

I dropship items. Can I use multiple origin zip codes?

No, the WooCommerce UPS extension currently uses one origin zip code to request quotes from UPS.

Does this create shipping labels and tracking codes?

No it does not. It provides the integration between UPS and WooCommerce, so you can calculate shipping rates for customers and collect the correct amount of payment in checkout.

You get shipping labels and tracking numbers directly from UPS or can buy a different plugin to handle that for you.

Rates are not in the correct currency

UPS will use the currency that is enabled on your account. So if your site uses a different currency then the one which is set on the account, the rates won’t be returned. If the debug setting is enabled this will be indicated with a warning like:
[UPS] Rate for Standard (UPS) is in USD but store currency is EUR.

If you need to convert these rates to the correct currency we would suggest using the Multi Currency extension and setting up a conversion rate for both the account currency and the store currency.

Troubleshooting

No rates returned/no rates available

• Confirm that your API credentials are correct.
• Enable development mode, or turn on WP_DEBUG to see debugging information on the cart page. This often reveals the issue.
• Check that your products have sizes and weights set – without this, the calculation cannot be performed.

Customize

If you would like to remove UPS as a shipping option for some shipping classes you can use the WooCommerce Conditional Shipping and Payments extension.

Or you can use code to do this.

You can add the following code to your functions.php. You need to change shipping classes used on the 14th line:

The post UPS Shipping Method first appeared on CODIBU.

USPS can calculate domestic and international parcel rates. This extension uses 2019 rates.

Requirements

• Your store must use US Dollars as its currency
• Server must have SimpleXML installed. Check with your hosting company if you’re unsure
• Base country must be the United States, Puerto Rico or US Virgin Islands

The extension primarily works with measurements in Inches (in) and weight in Pounds (lbs), but other units can be converted automatically.

Installation

1. Download the extension from your WooCommerce dashboard.
2. Go to Plugins > Add New > Upload and select the ZIP file you just downloaded.
3. Install Now, and then Activate.

API & Debug

Go to: WooCommerce > Settings > Shipping > USPS.

1. USPS User ID – You can use our USPS User ID (this is set automatically) or sign up for your own at Webtools account on USPS.com.
2. Debug Mode – Enable debug mode to show debugging info on your cart/checkout. This information is shown only to administrators who are logged in.

Setup and Configuration

1. Go to: WooCommerce > Settings > Shipping > Shipping Zones.
2. Add new Shipping Zone or Edit an existing zone to add the shipping method.
   
3. Select USPS from the dropdown, then Add shipping method.
   
4. Configure the settings:
   • Method Title – Name the shipping method. This is visible to customers.
   • Offer Rates – Choose whether to offer the customer only the cheapest rate or all returned rate options.
   • Fallback – Enter a fallback shipping cost (optional), if no rates are returned from the API. This allows the customer to check out if USPS does not return matching rates. When using this option, do not use a dollar sign, just enter the amount (ex: 12.50).
   •  Flat Rates
     1. Flat Rate Boxes and Envelopes – Enable this option to offer shipping using USPS Flat Rate services. Items are packed into the boxes/envelopes, and the customer is offered a single rate.
     2. Express Flat Rate Title – Give a custom name to the express flat rate.
     3. Priority Flat Rate Title – Give a custom name to the priority flat rate.
     4. Additional Fee – Enter a fee per box excluding tax, such as an amount (2.50) or a percentage (5%). Or leave blank to disable.
   •  API Rates – Check to enable non-flat rates using the USPS API. Default is all services available; or choose what to offer from the available shipping services listed below. You can adjust:
     1. Enable API Rates – This enables non-flat rate services.
     2. Origin Postcode – Postcode from where you ship. It is sent to the USPS API.
     3. Shipping Rates – Retail rates are standard costs, Commercial rates are discounted. If you want those rates to match those you get when printing labels with WooCommerce Shipping, set it to “Commercial rates”. Printing with WooCommerce Shipping automatically qualifies you for Commercial rates.
     4. Parcel Packing Method – See below for more detailed explanation.

Available Shipping Services

These services are included with the USPS Shipping extension:

Domestic

• First-Class Mail® Large Envelope
• First-Class Mail® Postcards
• First-Class Mail® Stamped Letter
• First-Class Package Service – Retail
• First-Class Postcard Stamped
• First-Class Large Postcards
• First-Class Keys and IDs
• First-Class Package Service
• First-Class Mail® Metered Letter
• First-Class Package Service Hold For Pickup
• Priority Mail Express Hold for Pickup
• Priority Mail Express
• Priority Mail Express Sunday/Holiday
• Retail Ground
• Media Mail®
• Library Mail
• Priority Mail®
• Priority Mail® Keys and IDs
• Priority Mail® Hold For Pickup
• Priority Mail® Regional Rate Box A (when commercial rates are used)
• Priority Mail® Regional Rate Box B (when commercial rates are used)

International

• Priority Mail Express International
• Priority Mail International®
• Global Express Guaranteed® (GXG)
• Global Express Guaranteed® Document
• Global Express Guaranteed® Non-Document Rectangular
• Global Express Guaranteed® Non-Document Non-Rectangular
• USPS GXG Envelope
• First Class Mail® International Letters
• First Class Mail® International Large Envelope
• International Postcards

Flat Rate Shipping Options

• Priority Mail Flat Rate – Envelopes (Legal, Letter, Gift Card, Padded, Small, Window) and Boxes (Small, Medium 1 and 2, Large, APO/DPO/FPO Large, Large Board Game, Prepaid Forever® Packaging)
• Priority Mail Express Flat Rate – Envelopes (Envelope, Legal, Padded) and Boxes (Top-Loading, Side-Loading)
• Priority Mail International Flat Rate® – Envelopes (Legal, Letter, Gift Card, Padded, Small, Window) and Boxes (Small, Medium 1 and 2, Large, APO/DPO/FPO Large, Large Board Game)

To enable any of these options:

Select the Standard Services option to ‘Retrieve Standard Service rates from the USPS API’.

You also have the option to rename the service and include a negative/positive price adjustment by the default currency or a percentage.

• Price adjustments ($) – Add a flat adjustment to the USPS service.
• Price adjustments (%) – Add a percentage adjustment to the USPS service.

Flat Rate Services

If enabled, the flat rate box option creates a single quote based on USPS Flat Rate Services. To do this, the system uses the box packer (explained below) applying USPS box dimensions. Packed boxes are then combined to offer a single rate (named by your ‘method title’).

Flat Rate Shipping prices come directly from USPS, and you cannot add or modify pricing for this option.

In the case of both Flat Rates and API Rates are used, USPS will return both but will reject one in favor of the other if it is cheaper for the same service.

Parcel Packing Method

There are three packing methods with USPS, and each affects the parcels you send to the API.

Per-Item

Each item in your cart (non-virtual) is sent to the USPS API. Quotes for all items are combined to calculate the final cost.

Pack into boxes

Items are packed into pre-defined boxes and sent to the API. We recommend this option. See Box Packing below for more information.

Weight based

Regular sized items (< 12 inches) are grouped and quoted for weights only. Large items ( > 12 inches) are quoted individually.

Box Packing

The box packer included with this shipping method lets you group items into packages for which you define height, width, length, weight and max-weight. Packing is mainly volume based but also considers item size.

Setting up box sizes

When using the ‘Recommended: Pack into boxes with weights and dimensions’ Parcel Packing Method, the Box Sizes table will appear. Click ‘Add Box’ to set up dimensions for your packages.

Name: This allows you to name your custom packages. This name will show in the Debug if that package is used.

L (in), W (in), H (in): The first set of dimensions are the outer dimensions of the package. These are the dimensions passed to the API. If you are working with a flat rate box via the API (i.e., Regional Boxes), use the API’s ‘inner dimensions’ for your box’s outer dimensions. Your box must ‘fit’ inside.

Inner L (in), Inner W (in), Inner H (in): The second set of dimensions are for the inner dimensions of the packaging. This should be the outer dimensions minus the thickness of the package walls. These dimensions are used for packing and items must fit within them (they cannot be the same size as the products, allow for a little extra room). Inner dimensions must be smaller than the first set of dimensions (outer dimensions).

Weight of Box (lbs): This is the weight of the empty box by itself. This weight is added to the total weight of the contents.

Max Weight (lbs): This is the maximum weight your box can hold. This includes the weight of the box and the contents. Setting this value as 0 would mean an unlimited box-weight.

Letter: This checkbox determines whether your package is a letter (envelope) or a box.

How the calculation works

The box packer:

1. Finds boxes that fit items being packed (uses H x W x D).
2. Packs all items into boxes (using volume).
3. Uses the smallest box fitting 100% of items *or* uses the highest % packed box, and then passes unpacked items back (and repeats the process)
4. Packs unpackable items alone, using item dimensions.
5. Returns all packed boxes.

Media Mail®

To enable Media Mail®, you must select the ‘Retrieve Standard Service rates from the USPS API’ option. You then have two options: a) You can do nothing, which allows any item to use Media Mail®; or b) if only some of your products are eligible for Media Mail®, you need to give each product a shipping class and restrict Media Mail® to use only that class or classes.

After setting up shipping classes, you can restrict settings in your Shipping Zone USPS rate:

Customer Usage

Customers can get quotes based on the address entered from two places:

• Cart page – by using the shipping calculator
• Checkout page – by filling in shipping and billing forms

Troubleshooting

No rates returned/no rates available

• Enable debug mode to see debugging info on the cart page. This often reveals the issue. To enable, go to WooCommerce > Settings > Shipping > USPS.
• Check that products have sizes and weights set – without this, the calculation cannot be performed.
• Go to: WooCommerce > Settings > General and check that your store’s base country is the United States and US Dollars is the currency.
• Check that the plugin is linked to USPS API. It uses wp_remote_post, which makes use of fsockopen/CURL.
• If API rate are enabled, make sure origin postcode is included.

If you need help with adding weights/dimensions, see:

Stamped Letter service not available

If packing items individually, please note the minimum size requirements for the contents of a letter envelope:

If the contents of the envelope(the product in the cart) are not within the minimum and maximum dimensions shown above, the Stamped Letter service will not be shown as available.

“UserName exceeds maximum length of 12 characters” error message

If you receive this error message when the debug mode is enabled, you need to use a shorter username.

Customize

Filter Flat Rate Services

To change the USPS package to envelope so dimensions are fixed, add this to your theme’s functions.php file:

To remove all the USPS Priority Flat Rate envelopes, leaving only the Small, Medium, and Large Flat Rate boxes, add this to your theme’s functions.php file:

The codes for each flat rate box can be found below:

Priority Mail Express
Priority Mail Express Flat Rate Envelope: d13
Priority Mail Express Legal Flat Rate Envelope: d30
Priority Mail Express Padded Flat Rate Envelope: d63

Priority Mail
Priority Mail Flat Rate Envelope: d16
Priority Mail Flat Rate Medium Box (Side Loading): d17
Priority Mail Flat Rate Medium Box (Top Loading): d17b
Priority Mail Flat Rate Large Box: d22
Priority Mail Flat Rate Large Box (Board Game): d22a
Priority Mail Flat Rate Small Box: d28
Priority Mail Padded Flat Rate Envelope: d29
Priority Mail Gift Card Flat Rate Envelope: d38
Priority Mail Window Flat Rate Envelope: d40
Priority Mail Small Flat Rate Envelope: d42
Priority Mail Legal Flat Rate Envelope: d44

International Priority Mail Express
Priority Mail Express Flat Rate Envelope: i13
Priority Mail Express Legal Flat Rate Envelope: i30
Priority Mail Express Padded Flat Rate Envelope: i63

International Priority Mail
Priority Mail Flat Rate Envelope: i8
Priority Mail Padded Flat Rate Envelope: i29
Priority Mail Flat Rate Small Box: i16
Priority Mail Flat Rate Medium Box (Side Loading): i9
Priority Mail Flat Rate Medium Box (Top Loading): i9b
Priority Mail Flat Rate Large Box (Top Loading): i11

Exclude a country from USPS rates

If you wish to exclude a country from receiving USPS rates, the easiest way is to use Shipping Zones (WooCommerce 2.6+). However if you wish, you can use the snippet below. Change US to the country code you’d like to exclude:

FAQ

Do Shipping Zones work with USPS Shipping?

Yes!

How can I get First Class Mail® International Large Envelope rates to display?

You need to use the Recommended parcel packing method and ensure that the Letter checkbox is ticked:

Additionally, per USPS, these services are not offered because they can’t be used for shipping merchandise. However, there is a way to override this setting in the extension with the following snippet:

The post USPS Shipping Method first appeared on CODIBU.

This guide will explain why this notice is displayed, likely causes of the issue, steps to diagnose the cause, and how to fix the problem or get help.

Scheduled Action Timeout Notice

As mentioned in Action Scheduler housekeeping, if an action has been “running” for more than five minutes, it is considered to have timed out and is marked as failed. This is because if an action has been running for that length of time, it is likely not actually running at all. When a subscription-related action fails due to a timeout, a notice is displayed in the admin dashboard.

Fixing Affected Subscriptions

Step 1 – Finding the Affected Subscription

The notice that appears after an action timeout contains a note with the subscription number and a link to the edit subscription page for that subscription. This can be used to investigate if there are issues with the last renewal payment for that subscription that need to be manually addressed.

Step 2 – Tracking When the Payment Process Was Affected

The first step to this is to see if payment was actually affected. This can be done by tracking when the payment process was affected.

Tracking the Renewal Process

For a renewal order, each stage of the renewal process is documented on the subscription in its notes. To view this process:

1. Go to the WooCommerce > Subscriptions > Edit Subscription screen
2. View the Subscription notes 

    

   
   

3. The normal process for a renewal follows:
   1. When a renewal is due, the subscription is moved to an On-hold status
   2. An order is created to record the renewal
   3. If the subscription is on automatic renewals, the order attempts to process payment and may mark complete
   4. Once payment is complete, the subscription is moved to Active status 

       

      
      

4. Each step above records the date and time at which it was processed.

Comparisons can be made between the payment process and the failed action in order to find out when the process timed out.

Failure Before Payment

If the renewal order was created but the payment was not marked complete, the process may have stalled before payment was processed. This can be indicated if the time of failure of the action, as found above, is close to the time of the creation of the renewal order.

To make sure that the payment was not captured, there are a couple steps to take.

1. Go to the created order, linked to in the Subscription notes
2. Check the Order notes on the order to see if the status changed and the payment was processed

    

   
   

3. Log in to the chosen payment gateway’s store account and check if the charge was captured for that order.

If there is no charge, then the processed stalled before payment was taken.

Failure After Payment

If payment was captured but the order was not marked Processing or Complete or the subscription was not transitioned to an Active status, then the process stalled after payment. This can be indicated if the time of failure of the action, as found above, occurs after the payment was marked complete.

Step 3 – Fixing Affected Subscriptions and Orders

Affected Before Payment

If payment was not captured:

1. On the existing renewal order, change the status to Cancelled and Update.
2. Set the subscription status to Active and Update.
3. Choose Process renewal from the subscription option dropdown.
4. This will then create a new renewal order, which should process as normal.

Affected After Payment

If payment was captured but the order and subscription were not updated:

1. If the renewal order was not marked Processing or Complete, change the status to the appropriate status. This will also update the subscription to Active.
2. If only the subscription was not transitioned, set the subscription status to Active.

Diagnosing the Cause

It’s impossible to programmatically identify the cause of a timeout. Instead, they always require manual investigated, which is why this notice is displayed. There are a number of possible causes, as outlined below, which should be explored to find the cause of the timeout.

Subscriptions Version

These timeouts, and thus the error notices, are expected to be extremely rare occurrences with Subscriptions 2.4.3 or newer.

If this notice appears on a site running a version of Subscriptions less than 2.4.3, the first step is to update the Subscriptions version.

If a site is currently running a Subscriptions version greater than or equal to 2.4.3, the version of Subscriptions at the time of the error should be checked. Even if Subscriptions has since been updated, it is important to note what version was running at the time the notice first appeared.

In order to check the version of Subscriptions running when the error occurred:

1. Review the WCS Upgrade log and the Failed Scheduled Actions log
2. Compare the time the error is logged in the Failed Scheduled Actions log to the version running at that time, as found in the WCS Upgrade log

If a Subscriptions version less than 2.4.3 was running at the time of the error and Subscriptions has since been updated, the underlying issue has likely been resolved.

If the version of Subscriptions was newer than that at the time of the error, further investigation is needed.

PHP Time Limit

The PHP time limit is the amount of time the server will spend on a single process before timing out. A time limit that is too short can cause processes to time out. A common default value is 30 seconds, and many managed hosts provide a longer timeout period.

To find the PHP time limit for your server:

1. Go to WooCommerce > Status to view the system status
2. Scroll down to the Server environment section
3. View the PHP time limit 

    

   
   

If this limit is below 30 seconds, we recommend increasing it to avoid scheduled action timeouts.

To change this limit, contact your hosting provider and discuss with them the best way to change the time limit if possible.

Large Number of Timeouts

This kind of notice and timeout is expected to be a very infrequent occurrence, and certainly not something that occurs repeatedly. In sites where there are dozens of timeouts or more, there is likely a critical underlying problem causing the timeouts that will need to be addressed.

To check the number of timeouts review the Failed Scheduled Actions log.

If there are many timeouts, please open a support ticket.

Further Help

If you would like further assistance, please open a support ticket.

In the support ticket, please include the system status, so we can find your site’s PHP time limit and plugin versions, and the name of your host, so we can investigate their specific server limitations. If in Step 1 you were able to determine the active version of Subscriptions at the time of the error, include this as well. Please also include an admin login so that we can access your site.

The post Subscriptions Scheduled Action Errors first appeared on CODIBU.

A number of issues can arise from disabling WooCommerce Subscriptions, such as for:

• Any dependent plugins
• Renewal payments
• Expiration upon the subscription’s end date
• Cancellation after the end of the prepaid term is reached
• Automatic retry of failed payments

Additionally, simply disabling the plugin may not completely stop all the actions associated with it, such as renewal payments.

Disabling Subscriptions Actions

If choosing to disable Subscriptions, steps will need to be taken to completely stop all associated actions. Scheduled actions, such as renewal payments, are processed in Subscriptions by a job queue library called Action Scheduler.

If another plugin, such as WooCommerce Memberships, Follow-up Emails, or WooCommerce version 3.5 or greater, is active on the site, then they will also be loading a version of Action Scheduler to process their own scheduled actions. In this case, the scheduled events for Subscriptions will continue to be processed, even if Subscriptions is inactive.

To check if another plugin is loading Action Scheduler:

1. Disable Subscriptions
2. Visit the admin screen at https://example.com/wp-admin/tools.php?page=action-scheduler, replacing example.com with your site’s URL

    

   
   

3. If the page loads, another plugin is using Action Scheduler

If nothing else is loading Action Scheduler, the queue will remain but be inactive. This means that it will still be there and continue to run if Action Scheduler is activated, either by re-activating Subscriptions or another plugin that uses Action Scheduler.

If Action Scheduler is still active and you do not want to disable the other plugins, it is possible to stop Action Scheduler from running. In order to completely stop Action Scheduler from running, download, install, and activate the Action Scheduler Disable Default Runner plugin. This plugin will stop the Action Scheduler queue from running altogether.

This means that all actions for all plugins using Action Scheduler will stop. If you need to continue processing actions for other plugins, please open a support ticket.

Disabling a Payment Gateway Plugin

It is also possible to disable a specific payment gateway plugin. If a gateway plugin is disabled while Subscriptions is active, those subscriptions that use that gateway will be converted to use manual renewals. This means that the subscriptions can be paid for, but the customer will need to log in and pay for the subscription using a different gateway, rather than a payment being automatically processed.

The post Disabling Subscriptions first appeared on CODIBU.