Core Features

1. Product Management: Create and manage unlimited product listings with options for unlimited variations, pricing, and descriptions. Support for 4 product types: Physical with shipping, physical without shipping, digital and services/events. Optionally track stock.
2. Order Management: Process and manage orders, handle refunds, print invoices and communicate with customers. Frontend order placement and backend manual order creation.
3. Shipping Options: Configure shipping methods, rates, handling and zones based on location and product type. Rates can be tiered and based on weight, price, quantity or flat. Support for 'rest of the world' shipping.
4. Tax Management: Calculate and apply taxes automatically based on location and product type. Prices can include/exclude taxes. Tax overrides can be added to product categories (collections) and/or shipping.
5. Analytics & Reporting: Gain insights into sales, customer behavior, and product performance. 
6. Payment Gateways: Integrate with numerous payment processors to securely accept online payments. Invoice, Stripe and PayPal included by default. Easily add your preferred gateway.

Optional Features

• Inventory Management: Track stock levels, manage back-orders, and set up low stock notifications.
• Product Categories (collections).
• Product Tags.
• Product Attributes (for product variants, e.g. colour, size, etc).
• Product Types:  'Phones', 'Books', 'Shirts' and so on.
• Product Brands: Create and manage shop product brands/vendors/manufacturers.
• Product Properties:  Further describe products based on various properties such as 'Colour', 'Grade', 'Weight', etc.
• Product Dimensions:  For instance, 'Centimetres', 'Kilograms', 'Litres', etc. For use with Product Properties.
• Downloads; Digital products or files that accompany a product such as 'tickets', 'manuals', and so on.
• Discounts:  Redeemed by customers or applied automatically at checkout. Support for four types: Fixed, Percentage, Shipping and Buy X get Y (last one is WIP). Discounts can be applied to whole order, parts of it, to select customers or countries.
• Customer Management: Create and manage unlimited customers. Can be created at checkout (using the API and/or hooks) or manually in the backend. Email customers directly from admin. Customers can have multiple addresses.
• Customer Groups: Create and manage unlimited customer groups Add customers to as many customer groups as needed. Customer groups can be targeted for marketing, promotions, etc.
• Legal Pages: Create and manage legal pages such as 'Shipping Policy', etc.
• Gift Cards: WIP.
• Move some pages from /admin/shop/ to a parent in the home tree.

With your help, we can add more features 😀!

I am new to ProcessWire and web development. I have just finished basic web development (frontend) and PHP. And now I am exploring ProcessWire. I want to develop a portfolio project for my uncle's business. He wants an e-commerce website with the following features:

1. All the common e-commerce functionalities.
2. B2B and B2C features.
3. CRM.
4. Some custom workflow implementation.
5. Some custom requirements like:
   1. An email verification feature for the clients.
   2. For registering a b2b client, they need to submit a registration form where they are supposed to upload a business document. The admin (shop owner) looks at the document and categorises the client as a b2b wholesaler or b2b retailer. 
   3. Wholesalers and retailer sees different prices for products, and similarly do the B2C clients.
   4. Appointment scheduling for consultation with payment for booking an appointment.

I am doing my best to explore all the resources in the ProcessWire website and documentation. It has been over a week I am looking for a perfect solution and I have come up to the following solutions:

1. The basic e-commerce functionalities can be handled by Modules like ProcessWire Commerce or RockCommerce.
2. Workflow implementation can be done using the hooks.

I am not experienced with the above solutions; I just looked at the website, the docs and found them from those resources. If my choices are wrong, please correct me with proper guidance. You may have already crossed the problems and issues that a new developer faces while implementing these modules.

For other functionalities, I am still actively looking for some solutions. If you are familiar with such cases, please guide me. I have a dream of starting my own digital agency, and I am selecting ProcessWire as my primary CMF for delivering the websites and web applications to my clients.

Thanks in advance!!

A big Thanks to the ProcessWire team for such a powerful and valuable open-source CMS framework!!!!

How can I upgrade to a more up-to-date/stable version, without having to rebuild the whole shop and inventory from scratch? When I click "check for updates", I get an error that "That module is not currently tracked by the modules directory".

Thank you for your help

George

$cart = $pwcommerce->cart;
 bd($cart);

$cart = '' and producing an error. Sorry, I know that this is free software but at least for me it is the same useless as was Mediamanager for which I paid without ever being able to use it thanks to the lack of documentation. And yes, I get the idea that for 100 EUR per hour you might help me set it up working.

--------------

New Site

• Install ProcessWire Commerce.
• The current (outdated and incomplete!) Padloper docs are still helpful. Note though that configuring ProcessWire Commerce is accessed via /admin/shop/configure-pwcommerce/.
• For template  files and hooks, please note the following:

Changes

Template Files

All instances of $padloper should be replaced by $pwcommerce. For instance $padloper->getCart() should become $pwcommerce->getCart(). 

All instances of 'pad_' should be replaced by 'pwcommerce_'. For instance 'pad_price_total' should become 'pwcommerce_price_total'.

Hooks

Your hooks, e.g. in ready.php should be renamed as follows: 

All instances of Padloper::someHookedMethod should become PwCommerce::someHookedMethod. Please note the spelling is case-sensitive.

Existing Site

• DO NOT UNINSTALL Padloper!
• DO NOT INSTALL ProcessWire Commerce!
• Download and install the Padloper to ProcessWire Commerce migration tool from this repo.
• Please READ all the instructions!
• Template Files: As above.
• Hooks: As above.

Any issues please let us know below. Include info about:

• ProcessWire version (please note ProcessWire Commerce/Padloper's admin GUI is broken in new admin theme,  i.e., ProcessWire 3.0.248 (or newer).
• Padloper version.
• Site language(s).
• PHP version.
• MySQL version.

For issues with the migration tool itself, please raise an issue in the project repo. Include the above environment information please.

Whilst I have thoroughly tested the migration tool (on a multilingual site), usage of the migration tool is at your own risk! 

Please note: I don't have it all figured out yet. With your help, we can figure it out together, including the contribution process.

Below are the things that currently need to be worked on.

Documentation:

• Frontend documentation - for frontend developers:  End-to-end how to work with ProcessWire Commerce in the frontend to build a shop. 
• Backend documentation - for shop editors. How to use the GUI to configure, build, run and manage a shop.
• API documentation - for documenting how ProcessWire Commerce is built, developing for it and contributing.

Still considering if/how to how to host documentation. Suggestions welcome.

Fix Bugs

• Identify, report and suggest bug fixes. Please file bug reports in the repo here - https://github.com/kongondo/ProcessWireCommerce/issues.
• Fork the project, fix bugs and submit PRs.

Tutorials

• Help write ProcessWire Commerce tutorials for different audiences.
• Help create demos.

Ecosystem

• Help grow the project.
• Star it on GitHub.
• Create add-ons.
• Build migration tools.
• Create a logo for ProcessWire Commerce.
• Help write unit tests (???)

Site Profiles

• Help develop an official, multi-lingual, modern site profile/theme to be used to showcase ProcessWire Commerce.
• Contribute site profiles or themes.

I have a repeaterfield on my product template. When I enable product variants the JS for InputfieldRepeater will trigger based on 'InputfieldRepeaterItem' class, causing errors and the variant's content gets hidden.

InputfieldPadloperRuntimeMarkup.module

// @note @kongondo: we need this class 'InputfieldRepeaterItem' so InputfieldImage.js will read the ajax postUrl from our data-editUrl here
$wrap->addClass('InputfieldPadloperRuntimeMarkupItem InputfieldNoFocus InputfieldRepeaterItem');

You have any ideas to prevent this? (I'd rather not change Fieldtype Repeater module itself, which I have done in the meanwhile)

I'll try my best to write the documentation. I need your help though. Please note the caveats in the 'open-sourcing Padloper' thread. I.e., I'll do what I can when I can. Your help is vey much appreciated. I'll prioritise assisting documentation contributors, to help point them in the right direction. 

Documentation should cover:

1. Frontend documentation - for frontend developers:  End-to-end how to work with ProcessWire Commerce in the frontend to build a shop. 
2. Backend documentation - for shop editors. How to use the GUI to configure, build, run and manage a shop.
3. API documentation - for documenting how ProcessWire Commerce is built, developing for it and contributing.

Thank you! You contribution is much appreciated!

It is official! Padloper is now ProcessWire Commerce.

ProcessWire Commerce is a free, open-source fully featured e-commerce module (plugin) for building and managing fully function online shops (stores) in ProcessWire. It is flexible, extensible, highly customisable, scalable, robust, multilingual by design and battle tested. 

Pro Support

ProcessWire Commerce is designed to be easy to develop with and to use. For some, you might need extra reassurance that professional help will be available if you need it. Or, you might have a question about how to perform a certain thing or wish to support the project to ensure that any issues are dealt with quickly. Or you might want to sponsor a particular feature. If this is you, Pro Support and custom development can be purchased from my website.

Community Support

These forums.

Donations

If you value my work or my work helps support your work or you just want to say thanks, please consider donating. Thanks!

Requests

Modalities are still being worked out. Please note:

1. I'll add features at my own pace; if and when I can (reasons for this discussed elsewhere in the forums). I'll focus on security, PRs and maintaining the project and major bug fixes.
2. I hope community will contribute.
3. Sponsored (pay for a feature) features: This can be by individuals or community driven. Please contact me for availability.

Known Bugs

1. ProcessWire Commerce Admin GUI is broken in the new admin theme, i.e., ProcessWire 3.0.248 (or newer).
2. Save + Exit and similar broken on some pages at some recent ProcessWire version. 
3. Manually order creation broken (backend).

Please file bug reports in the repo here - https://github.com/kongondo/ProcessWireCommerce/issues.

Contributing

This is a community project. All contributions are welcome! We are still working out how the 'how'.

Documentation

Please see this thread.

Other Important Stuff

1. Migrating from Padloper.
2. Community help request.

Tech Stack

1. ProcessWire (PHP).
2. Vanilla JS
3. htmx
4. Alpine JS
5. Tailwind CSS
6. MySQL

Download

Here you go!

Padloper 011 (aka Padloper 2 version 011) is ready for download.

Requirements

1. PHP>= 8.2.0
2. ProcessWire>=3.0.200

New Features

The main new feature is webhooks for order payments. This should work with any payment provider that supports webhooks. In Padloper, this is currently implemented for Stripe. Documentation to follow.

Maintenance

Lots of bug fixes related to language and variants. I'll add list here later.

Upgrading

Replace all files (not overwrite!). This is because some files have been deprecated, renamed or moved. Safest way to upgrade is to get rid of all existing Padloper files and folders under /site/modules/Padloper/ and then copy over the new 011 files and folders then do a module refresh.

Any questions or issues, please let me know.

Thanks.

I purchased Padloper this afternoon and was eager to test it out. Unfortunately due to errors I am stuck.

PW 2.0.242 on PHP 8.2.10 with only Language Support Module installed and one second language.
This is what I get when installing Shop:

As you can see, the SHOP menuitem in Admin is there.
So I ignored the error and tried to install some of the shop options, and got:

Out of clues I tried different PHP versions... but no success 😢

Due to sufficient database backups I always can go back to pre-installs.

Any hint?

I'm not sure if this worked before or it is broken since updating.

If I have a product that already has some variants, I can't seem to 'regenerate' additional variants. The button does not show. Could you check if this is the case? (I'm on version 11)

Next to that I'm also getting Uncaught TypeError: Cannot read properties of null (reading 'length') from Inputfieldtextags.js when I have more then 1 Attribute selected.

I have a question, how can I add a group of custom fields for a product, that is, I require the client to provide me with additional information when selecting a product.

For example, the client wants to buy a bracelet and wants to personalize it with his name, how do I make the bracelet product add an input field, where he can put the text he wants on his bracelet.

Do you have any examples in the Starter Demos?

Regards,

Padloper 010 (aka Padloper 2 version 010) is ready for download.

Requirements

1. PHP>= 8.2.0
2. ProcessWire>=3.0.200

Maintenance

Padloper 010 is mainly a maintenance release:

1. Fixes money rounding bugs found in Padloper 009 (and earlier). 
2. Adds the Money for PHP Library to handle monetary values in an easy and powerful way.
3. Fixes money math issues when prices include tax.
4. For the sake of internal maintenance, reorganises files and directory structure. 

Money Matters

Specifically regarding 'prices include tax', and I will be adding this to the docs, it is important that you display your prices in the frontend in a way that doesn't confuse consumers. This is not unique to Padloper but a general e-commerce issue. This means making careful decisions around displaying unit vs total prices as well as whether to include notes about potential rounding pence/cents issues in your shop's policy documents. Due to rounding issues (pence, cents, etc) when it comes to money, especially if quantity is more than 1, the math might look off. I.e., (item * quantity) + tax IS NOT NECESSARILY EQUAL TO (item + tax) * quantity. See this article for a thorough discussion.

Breaking Changes

There are a few unavoidable breaking changes due to code rationalisation.

API

Some API had to be changed for maintenance and usage simplicity reasons. This affects checkout, cart and discounts. For instance:

<?php

namespace ProcessWire;


# OLD API
$checkout = $padloper->checkout;
$response = $checkout->render($options);

# NEW API
// $response = $padloper->render($options);// this will be deprecated in a future release
$response = $padloper->renderCheckout($options);


##########

# OLD API
$cartRender = $padloper->cartRender;
$content = $cartRender->editCart();

# NEW API
$content = $padloper->editCart();

##########

# OLD API
$cartRender = $padloper->cartRender;
$content = $cartRender->viewCart();

# NEW API
$content = $padloper->viewCart();

HOOKS

Backend hooks rename:

// OLD NAMING FORMAT
PadloperProcessRenderXXX
e.g. PadloperProcessRenderOrders

// NEW NAMING FORMAT
PadloperAdminRenderXXX
e.g. PadloperAdminRenderOrders

Other hooks rename:

// OLD NAMING FORMAT
PadloperXXX::methodName
e.g. PadloperUtilities::getProductWeight, PadloperCart::getProductPrice

// NEW NAMING FORMAT
Padloper::methodName
e.g. Padloper::getProductWeight, Padloper::getProductPrice

Upgrading

Replace all files (not overwrite!). This is because some files have been deprecated, renamed or moved. Safest way to upgrade is to get rid of all existing Padloper files and folders under /site/modules/Padloper/ and then copy over the new 010 files and folders then do a module refresh.

New Features

The two new features are:

1. $padloper->money(); More information will be added to docs.
2. Bank Name as a property (bankAccountName) in the return value of $padloper->getShopBankDetails();. See request in this topic.

Next Steps

As mentioned in Padloper 009 topic, the focus now will be the documentation.

Any questions or issues, please let me know.

Thanks.

We are experiencing a lot of problems with orders that result in 500 errors after payment has been done and user is being redirected to the shop. First a couple but now very frequently. I found out this happens when users go to the website inside Facebook for example. They buy a product and get redirected to their default browser. (Usually the client is being redirected to their bank app) The browser is not aware of the session and the order is not being updated. This also happens when a user uses another browser then the default.

Using 009 and Stripe as payment provider.

I believe this is where it happens;
Cannot instantiate abstract class ProcessWire\PadloperPayment

TraitPadloperProcessOrderCaptureOrder.php:18
$this->setPaymentProvider($this->session->paymentProviderID);

I hope you can help me with this issue.

Important things to note:

1. You can validate and apply discounts programmatically or by capturing details using your custom form.
2. Padloper does not output a discount input since discounts are an optional feature.
3. Padloper provides a discount API that allows you to validate, apply, invalidate, remove, etc. discounts from an order.
4. You can submit your discount code form to the server however you wish, i.e. ajax or non-ajax.

The example below applies a discount with code 'SAVE10'. This is a 10% whole order discount. The example uses htmx (ajax). The form is in the checkout page but the ajax endpoint can be a single place, e.g. your home page.

Example Apply Discount Form Screenshots

Discount form on checkout page

Discount validation failed

Discount applied successfully

Example Apply Discount Ajax Form Handling 

Please see the comments in the code.

<?php

namespace ProcessWire;

// part of checkout template file. (/checkout/ page)

// HANDLE HTMX AJAX REQUESTS
if ($config->ajax) {
	$out = "";

	/////////////////////////
	if (!empty($input->post->order_apply_discount_code)) {
		// HANDLE DISCOUNTS APPLY/REDEEMING
		// -----------------------
		$out = "";
		// HANDLE REQUIRED INPUTS FOR DISCOUNT: code, email and country

		// 1. code
		// CUSTORM FORM TEXT INPUT FOR DISCOUNT CODE ('order_apply_discount_code')
		$dirtyCode = $input->post->order_apply_discount_code;
		$code = $sanitizer->sanitize($dirtyCode, "text,selectorValue");
		// 2. customer email
		$customerEmail = $sanitizer->email($input->post->order_apply_discount_customer_email);
		// 3. customer country
		$customerShippingCountryID = (int) $input->post->order_apply_discount_customer_shipping_country;


		if ($code && $customerEmail && $customerShippingCountryID) {
			// GOOD TO GO: all required values are present

			// VALIDATE AND SET THE DISCOUNT TO THE ORDER IF VALID
			/** @var WireData $result */
			$result = $padloper->validateAndSetDiscount($code, $customerEmail, $customerShippingCountryID);
			// -------
			// prepare message

			if ($result->isValid) {
				// discount validation passed
				$discountType = $result->discountType;
				$discountValue = $result->discountValue;

				if ($padloper->isFixedDiscount($discountType)) {
					// FIXED DISCOUNTS
					$discountValueAsCurrency = $padloper->getValueFormattedAsCurrencyForShop($discountValue);
					if ($padloper->isFixedPerOrderDiscount($discountType)) {
						// fixed per order discount
						$message = "A discount of {$discountValueAsCurrency} will be applied on the order at checkout.";
					} else {
						// fixed per item discount
						$message = "A discount of {$discountValueAsCurrency} will be applied on each eligible item at checkout.";
					}
				} elseif ($padloper->isPercentageDiscount($discountType)) {
					// PERCENTAGE DISCOUNTS
					// @note: you can be more spefic, e.g. whole order percentage versus selected items percentage discount. See the API docs for discount methods in Padloper
					$message = "A discount of {$discountValue}% will be applied on eligible items at checkout.";

				} elseif ($padloper->isFreeShippingDiscount($discountType)) {
					// FREE SHIPPING DISCOUNT
					$message = "Free shipping will be applied at checkout.";
				} else {
					// BOGO DISCOUNT
					// TODO

				}

				// just in case this discount has already been applied to this order
				if ($result->isAlreadyApplied) {
					$message = "This discount has already been applied to the order. {$message}";
				}
			} else {
				// DISCOUNT VALIDATION FAILED
				// @note: $result->notice will give you the exact reason validation failed.
				$message = "Sorry, the specified discount cannot be applied to this order. Please amend your basket and/or your customer details.";
			}
		} else {
			// MISSING DISCOUNT CODE AND/OR CUSTOMER EMAIL AND/OR CUSTOMER SHIPPING COUNTRY
			$message = "Please ensure that you specify a discount code, your email address and shipping country";
		}

		// OUTPUT RESPONSE FOR HTMX
		// @note: currently this message replaces existing ones; you can change this using htmx attributes such as oob, target, etc
		$out .= "<p class='mt-3'>$message</p>";

	}
	// -----------
	echo $out;
	// exit;
	$this->halt();
}


// ---------------
// USUAL CONTENT

// Primary content is the page body copy
$content = $page->body;

Thanks.

A fieldset for Bank Account Details that would store Bank Name, Sort Code and Account Number. This could then be automatically displayed on invoices, which is more or less a necessity to have on invoice if you are offering people to check out using Invoice as the payment option.

??

I'm just testing the tax calculations and the rounding doesn't seem to be handled quite right. 

The product is £3.50 and charge taxes on this product is enabled.
The store also has 'All taxes are included in stated prices' checked under tax settings and tax is set at 20%.

On cart page the total for 10 of this item is £35.

Once I get to the checkout confirmation the total after the tax calculation is £34.92 (see screenshot)

I am pleased to announce the release of Padloper 009! It has been a minute! I apologise for the delay. 

Padloper 009 introduces a number of new features, bug fixes (especially in Multilingual sites) and improves overall code efficiency.

Credits

Before I get into the details, I would like to say massive thanks for all who have contributed to this release in various ways. You have contacted me via the forums, via PM and via email to report bugs, test Padloper and suggest and sponsor new features. In particular, I would like to thank (in no specific order) @Spinbox, @alexm, @joe_g, @ank, @csaggo.com, @Jan Fromm, @Pete, @Sonia Margollé and @kalimati. Whilst I will not name those who contacted me privately, please accept my gratitude for your help. Apologies if I forgot to give anyone a mention! Massive thanks to @ryan for ProcessWire.

Padloper 009 is the most battle-tested Padloper yet! It has been tested and developed on high volume sites, sites that require lots of customisations and multilingual sites whose default language is not English. This robust development has helped fix bugs that I would not have been aware of otherwise as well as new ideas and features to improve the API, workflow and GUI of Padloper. Many of the suggested features have made it into this version. A few others are planned for the future.

There is a lot to talk about in this version. Below I’ll just give a summary of the changes and where necessary, create separate topics to discuss some of the new features.

Although Padloper 009 has undergone thorough testing, there might, inevitably, be some bugs. If you find one, please let me know in the forums under a separate topic. Thanks!

Changes

Features

Home

1. Customisable dashboard. You can render your own dashboard by creating a template partial named ‘padloper-process-render-shop-home.php’ and placing it at ’/site/templates/padloper/backend/padloper-process-render-shop-home.php’. Please see this thread for more details.

Orders

1. Customisable single order view. You can render your own dashboard by creating a template partial named ‘padloper-process-render-orders.php’ and placing it at ’/site/templates/padloper/backend/padloper-process-render-orders.php’. Please see this thread for more details.

2. Order status actions: Can be applied manually for order, payment and shipping status.

3. Quick filters e.g. ‘open’, ‘cancelled’, ‘abandoned’, etc. 

Products

1. Configurable pricing fields. Sales and Normal Price (e..g WooCommerce) vs Price and Compare Price (e.g. Shopify). Please see this topic for more details.

2. Categories can optionally be named ‘Collections’. Configurable via ‘/admin/shop/configure-padloper/’.

3. Bulk clone existing products.

4. Allow duplicate titles for products. 

Discounts (new)

1. 4 discount types: Orders, products, free shipping and BOGO (Buy One/Get One - unfinished; see below). Can be applied manually or automatically at checkout. Please see this thread for more details.

2. Add/remove via  ‘/admin/shop/configure-padloper/’. 

3. Part sponsored by Nifty Solutions. Thanks @Pete!

Customers and Customer Groups (new)

1. Customer creation and management. Please see this thread for more details.

2. Customer Groups. This feature will be expanded in the future. Please see the above thread for more info.

3. Add/remove via  ‘/admin/shop/configure-padloper/’. 

General Settings

1. Redone interface

2. Add ‘from email’ settings..

3. Add bank details settings..

4. Add order ‘least and most’ sales thresholds for orders’ quick filters.

5. Settings for ‘low stock’ and ‘price fields’ for products.

6. Add tab ‘user interface’ with settings for shop navigation (can have side menu and/or dropdown navigation) and search features (can use quick filters and/or advanced filter).

Other Backend

1. Quick filters on various dashboards.

2. Custom Dashboards for Home and Orders. More to be added in future.

Frontend

1. Custom shop root page. This allows you to move product-related pages and legal pages to live under a frontend-accessible page. Configurable via /admin/shop/configure-padloper/. Please see this topic for more details. For instance, /myshop/products/, /collections/, /products/, etc. This means you can directly access products on the frontend using their real paths/urls instead of using URL segments. This setting can be changed anytime via configuring Padloper at /admin/shop/configure-padloper/.

2. Custom URL segments for checkout out. E.g. instead of /checkout/success/, /checkout/confirmation/, etc., you can have custom, multilingual segments, e.g. /checkout/order-success/, /checkout/tilaus-menestys/, etc.

Miscellaneous

1. Various UI improvements.

2. Dashboards tables sorted by title by default.

Breaking Changes

1. Template partials for the frontend have been moved from /site/templates/padloper/ to /site/templates/padloper/frontend/.

Deprecated

1. ‘Search Feature’ on the home dashboard has been removed. Use ProcessWire in-built search instead. Padloper hooks into it to group padloper related results. 

2. PadloperProcessOrder::orderSaved now becomes PadloperProcessOrder::orderSavedHook.The new approach is to have all hooks in one please for easier maintenance and usage.

Bug Fixes

Please see the bug fixes topic.

How to Get It

Padloper 009 is available at https://processwireshop.pw/products/padloper/. For those renewing subscriptions, you will have to wait a bit, apologies. I am finalising work on renewal codes. I am hoping this will be ready by tomorrow. Any issues with the (revamped ?) site please let me know ?.

Upgrading

This is a major upgrade. Lots of code has been moved around. Best way to upgrade files is to empty the contents of the root Padloper folder and upload the contents of the new version there. There are no data model changes affecting existing features but as always, back up your site(s) first!

Next Steps

In addition to fixing any bugs that show in 009, these are the plans for the next 3-6 months, possibly more, in order of priority. No new features will be introduced until these are completed.

Documentation

Documentation will cover all topics including installation, backend and frontend use and the API. ‘How to guides’ will consist of short videos with corresponding textual content on a dedicated Padloper site.

Discounts

Finish work on the Buy One Get One (BOGO) Discount and automatic discounts.

Gift Cards

Finish work on Gift Cards.

Road Map

I will talk about this when the ‘next steps’ tasks have been completed.

Thanks!

Thanks,

Ank

thank you for your wonderful work so far! I'm almost done implementing a shop for a local café and roastery in germany. We try to archive a csv export on the order bulk edit menu and i couldn't really find a good way to implement this, could you help with that? Is there a hook to use?

The idea is to generate a csv file with shipment data of the selected orders if the state is changed to e.g. 'order delivered'. This could be used to generate dhl shipping labels. Then the shipping info doesn't have to be manually transferred.

Kind regards,
Guido