Notice something different? Meet the new Solidus brand!

Use Cases

Use cases

Product

Developers

Resources

Big player with big needs? See what Solidus can do for you.

Enterprise

Solutions

The foundation to stand up. The flexibility to stand out.

Features

Don’t reinvent the wheel—use our built-in integrations.

Integrations

Pricing plans designed to accommodate your growth.

Pricing

Documentation

Policies

Insights and announcements from the Solidus team.

Blog

Need a bit of help? Engage our trusted partners!

Partners

Join us if you want to chat—we're a friendly bunch!

Community

- [3.2.0 on GitHub](https://github.com/solidusio/solidus/releases/tag/v3.2.0)
- [3.2.0 on RubyGems](https://rubygems.org/gems/solidus/versions/3.2.0)

We've just released Solidus `v3.2.0`!

Thanks to all contributors, testers, and users who made this release possible.

This version's support will end in 18 months: 2024-02-18.

## What's next?

We're listening to developers all around the globe to make Solidus the best
e-commerce platform for you. That makes us aware of the areas we need to
improve, so expect a lot of work in:

- Making extensions first-class in the Solidus ecosystem.
- Improving the design of our core logic with a better service layer.
- Writing the documentation that you need to read.

## What changed on Solidus 3.2

Here's what changed in the last released version. If you have any trouble updating or you want to leave
some feedback, please use [this GitHub Discussion](https://github.com/solidusio/solidus/discussions/4161).

### Major changes

#### New Event Bus

A completely new Event Bus has been introduced. It has better support for async
subscribers, testability, observability, and many other features. It's been
developed as a separated gem, [omnes](https://github.com/nebulab/omnes). Check
its README for everything it supports!

Don't forget to consult the [upgrade guide from the legacy event system to
omnes](https://legacy-guides.solidus.io/customization/subscribing-to-events#upgrading-from-the-legacy-event-system).

While the legacy event system is still supported, it'll be removed on Solidus
v4.

#### New Solidus' starter frontend

For fresh Solidus applications, we now recommend you use
[solidus_starter_frontend](https://github.com/solidusio/solidus_starter_frontend).

solidus_frontend will be removed from the solidus meta-package gem in Solidus
v4. Furthermore, its code has been extracted from
https://github.com/solidusio/solidus to
https://github.com/solidusio/solidus_frontend. Once removed, you'll need to
explicitly add `solidus_frontend` to your Gemfile in order to continue using
it.

Meanwhile, the Solidus installer allows you to choose which one you want to use
as the storefront.

#### New guides

The guides that used to live at `solidusio/solidus` have been deprecated. You
can still find them at https://github.com/solidusio/legacy-guides, but a great
effort is in progress to make first-class documentation on
https://github.com/solidusio/edgeguides.

You can check them live in https://guides.solidus.io/.

### Other important changes

#### No more autoload of decorators in fresh applications

New Solidus applications won't autoload files matching `app/**/*_decorator*.rb`
pattern anymore. For previous Solidus applications, it's something that will
keep working as the responsible code was added to your `config/application.rb`
when Solidus was installed. That code is intended to work with Rails' classic
autoloader, deprecated on Rails 6 and removed on Rails 7. It keeps working
because of a [compatibility
layer](https://github.com/rails/rails/blob/296ef7a17221e81881e38b51aa2b014d7a28bac5/activesupport/lib/active_support/dependencies/require_dependency.rb)
which is also deprecated. However, it may be eventually removed, so you're
better off updating your `application.rb`  file. You should substitute:

```ruby
config.to_prepare do
  Dir.glob(Rails.root.join('app/**/*_decorator*.rb')) do |path|
    require_dependency(path)
  end
end
```

With:

```ruby
overrides = "#{Rails.root}/app/overrides" # use your actual directory here
Rails.autoloaders.main.ignore(overrides)
config.to_prepare do
  Dir.glob("#{overrides}/**/*_decorator*.rb").each do |override|
    load override
  end
end
```

You may also want to stop using the `decorator` naming, as it's no longer part
of Solidus recommendations (that files are monkey patches; they don't use the
[decorator pattern](https://en.wikipedia.org/wiki/Decorator_pattern)). E.g.,
you can place those files in `app/overrides/` and remove the `decorator`
suffix.

**Updated  2022-08-18**: If you have [deface](https://github.com/spree/deface) as one of your dependencies, the `app/overrides` path interferes with the directory it uses to load its overrides. To avoid double-loading and other issues, you should use a different directory. A good candidate could be `app/monkey_patches`.

#### Changes to the promotion system

Promotions with a `match_policy` of `any` are deprecated. If you have promotions
with such a match policy, try running the following rake task:

```bash
bin/rake solidus:split_promotions_with_any_match_policy
```

This will create separate promotions for each of the rules of your promotions with `any`
match policy, which should have the same outcome for customers.

Creating new promotions with `any` match policy is turned off by default. If you still want
to create promotions like that (knowing they will not be supported in the future), you can
set a temporary flag in your `config/initializers/spree.rb` file:

```ruby
# Allow creating new promotions with an `any` match policy. Unsupported in the future.
config.allow_promotions_any_match_policy = true
```

#### Static preference sources configured within `.to_prepare` blocks

[Rails 7 no longer supports referring autoloadable classes within an
initializer](https://guides.rubyonrails.org/autoloading_and_reloading_constants.html#autoload-on-boot-and-on-each-reload).

Because of that, we need to change the way we configure static preference sources.

Before:

```ruby
# config/initializers/spree.rb
Spree.config do |config|
  config.static_model_preferences.add(
    AmazingStore::AmazingPaymentMethod,
    'amazing_payment_method_credentials',
    credentials: ENV['AMAZING_PAYMENT_METHOD_CREDENTIALS'],
    server: Rails.env.production? ? 'production' : 'test',
    test_mode: !Rails.env.production?
  )
end
```

Now:

```ruby
# config/initializers/spree.rb
Rails.application.config.to_prepare do
  Spree::Config.static_model_preferences.add(
    AmazingStore::AmazingPaymentMethod,
    'amazing_payment_method_credentials',
    credentials: ENV['AMAZING_PAYMENT_METHOD_CREDENTIALS'],
    server: Rails.env.production? ? 'production' : 'test',
    test_mode: !Rails.env.production?
  )
end
```

### Other Changes

But there's also a lot of other stuff in this release! If you want to see the full list of the
changes made, plase take a look at the project's [CHANGELOG on GitHub](https://github.com/solidusio/solidus/blob/master/CHANGELOG.md).

We've just released Solidus v3.2.0! Thanks to all contributors, testers, and users who made this release possible. This version's support will end in 18 months: 2024-02-18.

Solidus v3.2

Hello, Solidus community—it’s been a while! 👋

This is Alessandro writing, with a recap of everything we’ve accomplished in the past quarter and a
sneak peek of what to expect in the next!

## Solidus 3.2 is around the corner!

First things first: a lot of you have been asking for a release date for Solidus 3.2 and, while we
don’t have a specific date in mind yet, I can tell you it will be available VERY soon.

At this point, we’re just ironing out the latest quirks, crossing our t's and dotting our i's, and
then we should be all set!

Bear a little more patience as we work to provide you this new release, which packs a ton of
improvements while being, as always, fully backwards compatible!

## What we did: Omnes, Starter FE, Rails 7 and Ruby 3.1

We took Q2 to finalize a few projects that had been long in the making: the next Solidus release
will bring a completely revamped event bus, a new starter FE, and Rails 7 and Ruby 3.1 support.

As always, you can consult the full list of
[Pull Requests](https://github.com/solidusio/solidus/pulls?q=is%3Apr+merged%3A2022-04-01..2022-06-30+is%3Aclosed)
for the nitty-gritty, or you can read the recap below for the highlights!

### Welcome Omnes, our new event bus!

Since its rollout in Solidus 2.9, we’ve been pushing the community to use the event bus to customize
Solidus whenever possible.

The event bus encourages orthogonal architectures where your customizations are independent of
Solidus’ domain model, leading to a cleaner and more maintainable codebase. We’ve been using it a
lot in our own Solidus apps, and it’s really improved the quality of our code.

Today, we’re excited to announce the next phase of our pub/sub architecture:
[Omnes](https://github.com/nebulab/omnes). Born out of the feedback that we have collected from the
community in the past two years, Omnes offers a cleaner, more intentional design, powerful
observability, built-in serialization and async processing and much more.

We have already ripped out the original Solidus event bus and[replaced it with Omnes](https://github.com/solidusio/solidus/pull/4342),
and we can’t wait to see what you’ll build with it! We’ll continue to improve Omnes and add new
events to the core—stay tuned!

### solidus_frontend is dead, long live solidus_starter_frontend!

This is not really a surprise since it’s been in the works for quite some time, but we have finally
[deprecated solidus_frontend](https://github.com/solidusio/solidus/pull/4320) in favor of the new
[solidus\_starter_frontend](https://github.com/solidusio/solidus_starter_frontend).

This has been in the making for a long time, and it’s already been announced in
[its own blogpost](/blog/getting-started-with-solidus-starter-frontend):
the new storefront marks the beginning of a new era for Solidus. The days of Deface and HTML
selectors are gone forever: instead, you now have complete control over the frontend of your Solidus
application.

We’ll continue to work on solidus\_starter\_frontend, with the goal of making it the perfect starting
point for Rails engineers that just want the _omakase_ experience, but we will also work on
providing better support for SPA architectures—more on that next quarter!

### Rails 7 and Ruby 3.1 support

Not much to say here, but we’ve been hard at work to ensure Solidus is fully compatible with
[Rails 7](https://github.com/solidusio/solidus/pull/4220) and [Ruby 3.1](https://github.com/solidusio/solidus/pull/4366),
so that you can benefit from the latest features and security enhancements.

## What to expect: docs, service objects and extensions

Our focus for Q3 will be mostly on improving some first-class citizens of the Solidus ecosystem: our
developer documentation, our service object architecture and our official extensions.

### Developer guides: better, faster, stronger!

As most of you know, we’ve been working on [completely revamping](https://guides.solidus.io) our
guides with the goal of providing a smoother, richer onboarding path to new Solidus users. The new
guides take a deep dive into all aspects of Solidus, allowing you to more easily implement advanced
customizations.

The guides are almost complete, which means the next few weeks will be about finalizing the content
and officially sunsetting the old documentation. We still have a couple of items on our bucket list
(e.g., being able to consult the docs for older Solidus versions), but we’re very close, so make
sure you don’t miss the announcement!

### How do you like them service objects?

If you’re in Slack, you know that we’ve been running a [survey](https://forms.gle/cPFkgt68kuo9fUWC6)
in the community to collect feedback about our service layer.

While the event bus handles a lot of scenarios, some customizations just need to be done the
old-fashioned way, and we want to make sure Solidus makes that experience as pleasant as possible.
That’s why we want to understand how people use and customize the business logic in Solidus, and
what they’d like us to improve.

If you have been using Solidus for a while and have feedback to share, there’s still time to fill
the survey—we promise to keep you posted about the results and key takeaways!

### Extensions: love them AND hate them

We’ve been talking to a lot of Solidus developers in the past couple of months about extensions, and
the same feedback keeps coming up: extensions manage to be both incredibly useful and incredibly
annoying at the same time.

They’re useful because they provide a strong starting point to solve a lot of complex eCommerce
challenges, and they’re annoying because they’re not given the same attention that is dedicated to
the rest of the ecosystem. When they work, it’s all sunshine and roses; when they don’t, it can
quickly turn into a maintenance nightmare.

We heard you, and we’ve already designed a solution: one that will allow us to keep the good bits of
extensions and get rid of the annoying bits. Sounds too good to be true? Well, you’ll find out more
very soon!

## That’s it!

Thanks for sticking with us so far!

As always, you’re encouraged to subscribe to our newsletter and join our Slack community, so you
don’t miss any important announcements.

We’ll see you next quarter with another roundup, but we’ll have plenty of things to share with you
in between: smaller updates, new releases and updates from all corners of the _Soli-verse_.

For now, have an amazing rest of your week!

— Alessandro and the Solidus team ❤️

Find out what happened in the Solidus ecosystem in Q2 2022!

Solidus Quarterly Roundup: Q2 2022

We're happy to introduce you to the new Solidus Starter Frontend app template.

## What is Solidus Starter Frontend?

Solidus Starter Frontend is the new frontend solution for Solidus. It aims to
deliver

* a minimal, semantic and accessible HTML skeleton
* a reusable component based architecture
* simple SASS styling strictly based on BEM
* frontend functionality written in vanilla JavaScript

## How is Solidus Starter Frontend different from the Solidus Frontend gem?

Based on our experience building eCommerce applications, we see that the vast
majority of stores heavily customize their storefront. As a result, the
controllers and views of `solidus_frontend` are essentially public API of the
gem. This makes it difficult to make improvements to `solidus_frontend` without
breaking existing Solidus apps. This has prevented `solidus_frontend` from
growing at the same pace as other Solidus components.

Since storefronts are heavily customized, we've come to the following
conclusions:

1. Decoupling the frontend gem from Solidus would allow us to improve the
frontend without breaking apps that depend on Solidus.

2. We can assume that once an app customizes its frontend, the app would no
longer need to continue depending on the frontend gem, since it may no longer
be able to keep its customizations compatible with the gem.

With these in mind, we've chosen to change `solidus_frontend` from a gem to a
Rails application template. As a template, we can make improvements to the
frontend for new applications to use. At the same time, we don't have to worry
about these improvements causing incompatibilities to existing Solidus
applications.

Thus, Solidus Starter Frontend is born.

## How do I install Solidus Starter Frontend on a new Rails app?

Currently, the `solidus` gem includes the legacy `solidus_frontend` gem. To
install `solidus` without `solidus_frontend`, we'll need to manually
add the rest of the Solidus components individually:

```sh
rails new store --skip-javascript
cd store
bundle add solidus_core solidus_backend solidus_api solidus_sample
bin/rails generate solidus:install --auto-accept
```

Once done, all we need to do is to run the following line:

```sh
LOCATION="https://raw.githubusercontent.com/solidusio/solidus_starter_frontend/master/template.rb" \
  bin/rails app:template
```

## What can I expect to see once the frontend is installed?

*Home page*
![Home page](https://cdn.sanity.io/images/9g5nd6b4/production/f5dd884327d1a925742c483fc2443444fb65e28f-2192x1096.png?fit=clip&q=60)

*Product page*
![Product page](https://cdn.sanity.io/images/9g5nd6b4/production/93b529bf4d3a6ddc3128be75b154987c2b0c8fd5-1920x980.png?fit=clip&q=60)

*Cart page*
![Cart page](https://cdn.sanity.io/images/9g5nd6b4/production/4f8584d45e2eb64f032e943dcc97eb921e612d76-1920x920.png?fit=clip&q=60)

*Login Page*
![Login Page](https://cdn.sanity.io/images/9g5nd6b4/production/6be640b1b2a218c5828b46fe90774791a9da6d1b-2192x1126.png?fit=clip&q=60)

*Checkout - Address page*
![Checkout - Address page](https://cdn.sanity.io/images/9g5nd6b4/production/3b3aa95d6ecb3ac6278605caedb79891e3693cf1-2192x1126.png?fit=clip&q=60)

*Checkout - Delivery page*
![Checkout - Delivery page](https://cdn.sanity.io/images/9g5nd6b4/production/36ae21f1a2ce233b5779696f59aa7ccc9184d717-2192x1066.png?fit=clip&q=60)

*Checkout - Payment page*
![Checkout - Payment page](https://cdn.sanity.io/images/9g5nd6b4/production/5ba9d59a5ded7446dbc2f92de2ff80ba33589622-2192x1066.png?fit=clip)

*Checkout - Confirm page*
![Checkout - Confirm page](https://cdn.sanity.io/images/9g5nd6b4/production/d195fbb75a28052fbf3c090769ed51a3729b101d-2192x1126.png?fit=clip)

*Checkout - Complete page*
![Checkout - Complete page](https://cdn.sanity.io/images/9g5nd6b4/production/97119029bee33799506bf23d8a319cd681acbc86-2192x1126.png?fit=clip)


In addition to generating views for authentication and storefront functionality,
the application template will also generate

* Mailers with their corresponding views
* [View components](https://viewcomponent.org) for complex presentational logic
* Unit and integration specs for testing the frontend

## What's next for Solidus Starter Frontend?

For Solidus 4, SolidusStarterFrontend will become the recommended option for
building the storefront of a new Solidus app. We're planning to remove
SolidusFrontend from the solidus meta-package gem and move its code to a new
repo. If your app depends on SolidusFrontend, you'll need to explicitly add
`solidus_frontend` to your Gemfile in order to continue using it.

We are also still working on a solution to make the extensions compatible with
this new frontend.

## Where can I find more information on Solidus Starter Frontend?

You can check out the accompanying [screencast](https://youtu.be/UpMYAH9SBCg) of
this blog post in our Solidus
[YouTube channel](https://www.youtube.com/channel/UCiFcxyt11T6QIIDPk2w0Jjw).
You can also find the
[repo](https://github.com/solidusio/solidus_starter_frontend)
of Solidus Starter Frontend on GitHub.

We're happy to introduce you to the new `solidus_starter_frontend` app template.

Getting Started with Solidus Starter Frontend

We've released Solidus [3.1.6](https://github.com/solidusio/solidus/releases/tag/v3.1.6), [3.0.6](https://github.com/solidusio/solidus/releases/tag/v3.0.6) and [2.11.16](https://github.com/solidusio/solidus/releases/tag/v2.11.16) to address a security vulnerability ([GHSA-8639-qx56-r428](https://github.com/solidusio/solidus/security/advisories/GHSA-8639-qx56-r428)) affecting all versions of Solidus.

You can read about GHSA-8639-qx56-r428 on the [solidus mailing list](https://groups.google.com/forum/#!forum/solidus-security).

If you have any questions about how to secure your site please stop by our Slack [http://slack.solidus.io/](http://slack.solidus.io/).

Have a nice day!

New Solidus releases to address GHSA-8639-qx56-r428. Please, update your store soon.

New Solidus releases to address a security vulnerability

PayPal has contributed to Solidus massively over the last few years, helping us revitalize both `solidus_paypal_commerce_platform` and `solidus_paypal_braintree` extensions. Entering into the next PayPal phase that we promised, we are excited that both extensions now support Venmo!

This latest addition to their SDK and Braintree allows another streamlined payment option for your customers at no additional cost.

Having multiple finance options is vital as it allows for a higher conversion rate. As well as this, Venmo offers some unique features.

### What is Venmo?
Venmo allows customers to make payments in a mobile app effortlessly, and uniquely, the buyer has the [option to split or share the purchase](https://help.venmo.com/hc/en-us/articles/217532327-Splitting-Sharing-Purchases).

It is currently available to only US PayPal merchants and buyers. However, with its recent rise, **every 1 in 5** US citizens already use it each year.

If you meet the [eligibility requirements](https://developer.paypal.com/docs/business/checkout/pay-with-venmo/#eligibility) you can integrate Venmo into your store where buyers will gain the following experiences:

#### Mobile checkout:
- Buyer clicks the Venmo button and their mobile device switches to the Venmo app.
- Buyer sees a payment review on the Venmo app and completes it.
- Buyer gets switched back to your website to complete the payment.

![Venmo checkout process on mobile](https://cdn.sanity.io/images/9g5nd6b4/production/7a18725321b62a4e36f79a72e9777560ec1b30e7-2648x937.png?fit=clip&q=60)

#### Desktop checkout:
- Buyer clicks the Venmo button on the desktop to generate a QR code.
- Buyer scans the QR code from the Venmo mobile app.
- Buyer completes the payment review on the Venmo app.
- Buyer completes the payment by the website on desktop.

![Venmo checkout process on desktop](https://cdn.sanity.io/images/9g5nd6b4/production/a2f7c3b9ab89405a463745fbec6d4f9d03ccf436-3230x1664.png?fit=clip&q=60)

*Simple!*

### How to integrate Venmo?
If you don't have [solidus_paypal_braintree](https://github.com/solidusio/solidus_paypal_braintree#installation)  or [solidus_paypal_commerce_platform](https://github.com/solidusio-contrib/solidus_paypal_commerce_platform#installation) installed and setup already - do that first and then continue with the integration. [Unsure which to install?](https://solidus.io/blog/2020/11/24/using-paypal-with-solidus.html)

#### SolidusPaypalBraintree
For this extension, Venmo is accessible to your payment page by two ways:
1. Braintree native Venmo integration; and
2. Enabling Venmo as a funding source/finance option on your PayPal buttons if you are using "checkout" `paypal_flow`.

The benefit of the native Braintree integration is that it supports vaulting unlike Venmo as a funding source.

First, update the extension by running `bundle upgrade --conservative solidus_paypal_braintree`.

##### Native Braintree Venmo integration
1. Enable Venmo in your [Braintree account](https://developer.paypal.com/braintree/articles/guides/payment-methods/venmo#setup)(sandbox and production).
2. Enable Venmo in the admin panel:
	 - Click `Braintree`.
	 - Tick `Venmo`.
	 - Click `Update`.
3. Ensure the `_venmo_button.html.erb` partial is being rendered appropriately.

If your store is a SPA or uses this on checkout, you may need to set your Braintree payment method `venmo_new_tab_support` preference to `false`.

##### Venmo as a PayPal funding option
If PayPal is enabled already and you are using the "checkout" `paypal_flow`. The Braintree store PayPal messaging preference must be set to `false` for Venmo to be available.

1. Go to the admin panel.
2. Click `Settings` > `Payments`.
3. Click the edit icon on your `Solidus PayPal Braintree` payment method.
4. Tick the `Enable venmo funding` checkbox.
5. Click `Update`.

#### SolidusPaypalCommercePlatform
First, update the extension by running `bundle upgrade --conservative solidus_paypal_commerce_platform`.

1. Go to the admin panel.
2. Click `Settings` > `Payments`.
3. Click the edit icon on your `Solidus PayPal Braintree` payment method.
4. Set `Venmo standalone` to:
		- `enabled` (adds the Venmo button under other PayPal funding sources); or
		- `render only standalone` (only shows the Venmo button and hides other PayPal funding sources - only recommended when you only have US customers).

5. Untick `Display credit messaging` (must be disabled for Venmo to be available).
6. Click `Update`.

#### Integrated!
You should now see a Venmo button on the payment page! Either with other PayPal buttons or on its own depending on your extension and integration choice.

![Venmo checkout button](https://cdn.sanity.io/images/9g5nd6b4/production/98a60e2f36488c1c2777b35b4953fd4a5fc07f2d-680x131.png?fit=clip)

### Testing Venmo
We recommend testing all of the following. Ensure that:

- the Venmo checkout button opens a modal;
- you can do a full transaction on checkout (see below);
- you can void and refund Venmo transactions; and
- if you are using the native Braintree Venmo integration:
	1. you can save the payment source to a user's wallet;
	2. saved Venmo wallet payment sources appear correctly; and
	3. saved Venmo payment sources can be reused for another order.

#### Testing a full transaction when Venmo is a PayPal funding source:
By default, PayPal looks at the buyer's IP geolocation to determine whether Venmo should be available. However, you may want to mock your country to test the Venmo integration.
Thanks to the new `force_buyer_country` preference available to both extension's `Payment Method`, this is simple:
1. Go to your extension's payment method's preferences
2. Set the `force buyer country` preference to any [https://developer.paypal.com/docs/business/javascript-sdk/javascript-sdk-configuration/#locale](country code that PayPal allows); such as "US" or "IT".
3. Click the `Update` button.

_This preference has no effect on production._

#### Testing a full transaction with Braintree's native Venmo integration:
You'll need the Venmo app in order to fully test the integration. However, if you are outside of the US, this is not an option. You can fake the tokenization by:
- Altering the `venmo_button.js` file to call the `handleVenmoSuccess` function instead of tokenizing and inserting the fake nonce appropriately; or
- Manually:
	1. Update the `#venmo_payment_method_nonce` hidden input value to "fake-venmo-account-nonce".
	2. Remove the `disabled` attribute from each `.venmo-fields` input.
	3. If you have enabled Credit Cards (hosted fields):
			- Add the `disabled` attribute to each `.hosted-fields` input.
			- Remove its submit button listener: `$('#checkout_form_payment').off('submit')`.

### The Future
Thanks to PayPal and Braintree SDK additions and continued support to Solidus and extensions, you will continue to see new exciting features soon! So stay tuned and continue building your incredible Solidus store!

Venmo, the last payment addition to solidus_paypal_braintree or solidus_paypal_commerce_platform. Learn how to add it to your Solidus store.


Add Venmo To Your Solidus Store

Hey everyone! Today we are excited to share with you Solidus’ newly forged partnership with [Afterpay](https://www.afterpay.com/).

[Afterpay](https://www.afterpay.com/) is a payment method that allows your customers to pay for their cart in 4 interest-free installments.

![](https://cdn.sanity.io/images/9g5nd6b4/production/0452759e7204398bb21095a180b899314bb457ab-2804x844.png?fit=clip&q=60)

The [Solidus and Afterpay](https://github.com/nebulab/solidus_afterpay) extension makes it very easy to add the Afterpay payment method to your store.

You are able to use the extension both with Solidus and Solidus APIs since the shared endpoints can be consumed by a React/VueJS application.

## Solidus Afterpay Configuration

After the installation, you will be able to configure the Afterpay payment method using the Solidus admin panel.

![](https://cdn.sanity.io/images/9g5nd6b4/production/f2fd4d0c80944e109de28115582c706bc3b61e54-1908x1682.png?fit=clip&q=60)

On this page, you can update the Afterpay credentials and choose where the customer can make the payment. You have two options changeable by the `popup window` checkbox:

- redirect the customer to the Afterpay panel;
- show the Afterpay popup inside your application

The Afterpay credentials (merchant ID and secret key) will be given to you once you go through the [retailer application on the Afterpay website](https://get.afterpay.com/app/).

## Checkout

If the configuration is correct, the customer will see the Afterpay payment method during the checkout payment step.

![](https://cdn.sanity.io/images/9g5nd6b4/production/76936d0fd682a24987df7a5acbe938299dae1b19-1696x1652.png?fit=clip&q=60)

Users can log in or create an Afterpay account without leaving your e-commerce site and will pay the first installment (25%) at the time of the order. Afterpay will pay the merchant the full amount of the order minus any fees. See [Getting Paid](https://developers.afterpay.com/afterpay-online/docs/getting-paid). In this step, there will be information about payments and future charges. If Afterpay authorization is successful, the user is redirected to the order confirmation checkout step to complete the order.

![](https://cdn.sanity.io/images/9g5nd6b4/production/99fea4d557d3748fa98104e48010ec8845bd8dc0-1688x1686.png?fit=clip&q=60)

When the order is placed and the first installment is charged, the customer will receive the order confirmation from Afterpay.

![](https://cdn.sanity.io/images/9g5nd6b4/production/b9ab12f84acd4743fc274aa1b3768ae36b19c2ab-1152x1322.png?fit=clip&q=60)

## Express checkout

Adding this partial inside your cart view, the [Afterpay Express Checkout](https://developers.afterpay.com/afterpay-online/docs/what-is-express-checkout-1) button is shown and the checkout is handled by Afterpay.

```
<%= render "solidus_afterpay/afterpay_checkout_button" %>
```

![](https://cdn.sanity.io/images/9g5nd6b4/production/a95c5c12f3000a886f07bc1a1e4bf9c443ea97b5-1670x1430.png?fit=clip&q=60)
![](https://cdn.sanity.io/images/9g5nd6b4/production/ec8bb7ae24387074e1820a77dbd35da41166725e-1666x1596.png?fit=clip&q=60)

Each time a customer changes the delivery address using the Afterpay express checkout modal, Solidus calculates the shipping rates based on the available shipping methods. You can also [customize](https://github.com/nebulab/solidus_afterpay#customizing-shipping-rate-builder) this behavior by building a custom service object.

## Deferred VS Immediate Payment Flow

Afterpay allows you to configure the payment method choosing between the [deferred payment flow and the immediate payment flow](https://developers.afterpay.com/afterpay-online/docs/api-calls-and-payment-flows).
This option is related to the Solidus auto-capture payment flow:

- if the auto-capture is disabled, the application will use the deferred payment flow;
- if the auto-capture is enabled, the application will use the immediate payment flow

In both cases, the first installment is charged by Afterpay when the order is placed. The difference is in when funds are settled between the merchant and Afterpay.

- in the immediate payment (capture) flow, the capture is processed at the time of placing the order, and the funds are settled with the merchant next business day (based on the order date);
- in the deferred payment flow, the captures (full/partial) are processed as items in the order are shipped, and the corresponding funds are settled with the merchant next business day (based on the capture date)

## Afterpay Messaging

Afterpay offers an on-site messaging component to notify customers that Afterpay installments are available. Ensuring customers are aware of an installment payment option on product and cart pages helps increase conversation rates and increase average order values.

![](https://cdn.sanity.io/images/9g5nd6b4/production/5e3e5c6dc9b7a8d6e9e385d73a90ca34542e6b08-624x316.png?fit=clip&q=60)

You can configure a min and a max price to show the messaging below products not available with Afterpay.

## Solidus Admin Panel

Inside the Solidus admin panel, you have the ability to capture and refund an Afterpay payment.

![](https://cdn.sanity.io/images/9g5nd6b4/production/ffdcaa92078d4213669b9eefdcf282ad4dd03203-1232x288.png?fit=clip&q=60)

Afterpay charges the customer the first installment at time of order. When you capture the order after fulfillment (if using deferred capture), the funds will be settled with you the next business day by Afterpay.

If you refund the user, the future installments are cancelled and any money charged to the consumer will be refunded

## The Bottom Line

That's all! As you can see, the configuration is very simple and you can integrate Afterpay with minimal effort. Just get the ball rolling!

If you're interested in supporting the work we do at Solidus, please consider making a donation on the OpenCollective - every little bit helps! And as a last note - sincere thanks to Afterpay for making all of this possible.

_Late fees may apply. Eligibility criteria apply. See [afterpay.com](http://www.afterpay.com/) for more details. Loans to California residents made or arranged pursuant to a California Finance Lenders Law license._

Hey everyone! Today we are excited to share with you Solidus’ newly forged partnership with Afterpay. This payment method allows your customers to pay for their cart in 4 interest-free instalments.

Using Afterpay with Solidus

We've released Solidus [3.1.5](https://github.com/solidusio/solidus/releases/tag/v3.1.5), [3.0.5](https://github.com/solidusio/solidus/releases/tag/v3.0.5) and [2.11.14](https://github.com/solidusio/solidus/releases/tag/v2.11.14) to address a security vulnerability ([GHSA-h3fg-h5v3-vf8m](https://github.com/solidusio/solidus/security/advisories/GHSA-h3fg-h5v3-vf8m)) affecting all versions of Solidus.

You can read about GHSA-h3fg-h5v3-vf8m on the [solidus mailing list](https://groups.google.com/forum/#!forum/solidus-security).

If you have any questions about how to secure your site please stop by our Slack [http://slack.solidus.io/](http://slack.solidus.io/).

Have a nice day!

New Solidus releases to address GHSA-qxmr-qxh6-2cc9. Please, update your store soon.


We've released Solidus [3.1.4](https://github.com/solidusio/solidus/releases/tag/v3.1.4), [3.0.4](https://github.com/solidusio/solidus/releases/tag/v3.0.4) and [2.11.13](https://github.com/solidusio/solidus/releases/tag/v2.11.13) to address a security vulnerability ([GHSA-xm34-v85h-9pg2](https://github.com/solidusio/solidus/security/advisories/GHSA-qxmr-qxh6-2cc9)) affecting all versions of Solidus.

You can read about GHSA-qxmr-qxh6-2cc9 on the [solidus mailing list](https://groups.google.com/forum/#!forum/solidus-security).

If you have any questions about how to secure your site please stop by our Slack [http://slack.solidus.io/](http://slack.solidus.io/).

Have a nice day!

New Solidus releases to address GHSA-qxmr-qxh6-2cc9. Please, update your store soon.

It's official! [Solidus Conf 7](https://conf.solidus.io/solidus-conf-7-solid-us-support-open-source/) will be on January 27th, 2022 with a bonus community day on January 28th. The conference will be entirely remote, held on Gather.town, and we couldn't be more excited to hear from the experts and spend time with the community.

The past few years have been arduous for so many people, with new obstacles arising every day. It's been difficult to not be able to get together in person and have the conferences we've gotten used to over the past five years. We were very grateful to Sean Denny and [Nebulab](https://nebulab.com/) for planning Solidus Conf 2020 last year. When some people thought we wouldn't be able to have a conference at all during the pandemic, he kept the momentum going and led the organization of a great remote event. (And he even jump-started the organization effort for this year's conference too! Thanks again Sean!)

While it would have been great to be able to return to being in-person for this upcoming conference, we're confident that hosting it on Gather.town will ensure a unique and positive experience that everyone can enjoy - regardless of location! You can visit [Gather.town](https://gather.town/app) to explore the app ahead of time, and learn more about what to expect.

At Solidus Conf, the speakers never disappoint, and this year is setting up to be no different. Jared Norman (Core Solidus Team Member), and Chris Todorov, both from [Super Good Software](https://supergood.software/)will be speaking, along with Marc Busqué (Core Solidus Team Member) from [Nebulab](https://nebulab.com/), Peter Berkenbosch, Thomas Sample from [Karma Creative](https://karmacreative.io/), and Daniel Pritchett from [Rebellion Defense](https://rebelliondefense.com/). We can't wait to hear from all of these extraordinary Solidus developers, along with those who have yet to confirm. Stay Tuned as we release the rest of the speaker list over the next coming weeks. You can find an up-to-date list of speakers and their details on the [Solidus Conf 7](https://conf.solidus.io/solidus-conf-7-solid-us-support-open-source/) website. If you, or someone you know has an idea for a great talk, please reach out and let us know - we would love to hear from you!

With everything that's been happening, we feel extremely fortunate to have the Solidus community to help provide support and comradery. The Solidus Stakeholders have been meeting at least every other week since 2018, and are passionate about keeping the platform moving forward. As an open source community, it's vital to keep the communication lines open, and the conference is the perfect place to make sure everyone is up to speed. We encourage each and every attendee to join the Solidus Slack Channel, and consider becoming a stakeholder themselves, because it really is all of us that make Solidus what it is, and can keep the platform progressing and thriving.

This year Thomas Sample and Karma Creative led the charge so far in organizing the conference, with expert design and development help from Michela Frecchiami and Nebulab. But with two months to go, we still are in need of additional hands and minds! Speaking of which, shout out to Chris Todorov from Super Good Software who is joining the organization team. Thanks Chris! -- If you are interested in helping with the organization, graphic design, web development, marketing, or day-of responsibilities at Solidus Conf 7, please reach out and let us know. In recognition, everyone involved will be listed as a contributor at the bottom of the conference website and receive some special organizer swag.

You can find additional information, and buy your tickets on the [Solidus Conf 7](https://conf.solidus.io/solidus-conf-7-solid-us-support-open-source/) website - we can't wait to see you again, learn, and have some fun together!

And have you thought about Sponsoring? You'll get $1 tickets and a bunch of other awesome benefits. And best of all, if you're already an Open Collective monthly Sponsor, you're also already a Solidus Conf 7 Sponsor! -- Open Collective Sponsors this year will automatically receive a corresponding sponsorship matching the level of their monthly donation!!

It's official! Solidus Conf 7 will be on January 27th, 2022 with a bonus community day on January 28th. The conference will be entirely remote, held on Gather.town  


Announcing Solidus Conf 7

We've released `solidus_auth_devise` [2.5.4](https://github.com/solidusio/solidus_auth_devise/releases/tag/v2.5.4) to address a security vulnerability (GHSA-xm34-v85h-9pg2) affecting all versions of `solidus_auth_devise`.

We've also released Solidus [3.1.3](https://github.com/solidusio/solidus/releases/tag/v3.1.3), [3.0.3](https://github.com/solidusio/solidus/releases/tag/v3.0.3) and [2.11.12](https://github.com/solidusio/solidus/releases/tag/v2.11.12). They just contain a patch in case you're unable to update `solidus_auth_devise`.

You can read about GHSA-xm34-v85h-9pg2 on the [solidus mailing list](https://groups.google.com/forum/#!forum/solidus-security).

If you have any questions about how to secure your site please stop by our Slack [https://slack.solidus.io/](http://slack.solidus.io/).

Have a nice day!

New Solidus releases to address GHSA-xm34-v85h-9pg2. Please, update your store soon.

New solidus_auth_devise & Solidus releases to address a severe security vulnerability

- [3.1.0 on GitHub](https://github.com/solidusio/solidus/releases/tag/v3.1.0)
- [3.1.0 on RubyGems](https://rubygems.org/gems/solidus/versions/3.1.0)

We've just released Solidus `v3.1.0`!

Thanks to all contributors, testers, and users who made this release possible.

This version's support will end in 18 months: 2023-03-10.

## What's next?

For the next minor release (3.2.0), we plan to make huge changes to the Event Bus, in order to provide
a solid architecture with a set of tools that will help developers use this feature. We are planning
to release a new adapter along with the current one, to allow Solidus' users some time to switch, which
could require some code change in the host applications.

The main features of the new Event Bus Adapter are:

- Isolation from `ActiveSupport::Notification`.
- Better observability for event-generated flows.
- Better testability.
- More robust events registration.

## What changed on Solidus 3.1

Here's what changed in the last released version. If you have any trouble updating or you want to leave
some feedback, please use [this GitHub Discussion](https://github.com/solidusio/solidus/discussions/4161).

### Major changes

**`Spree.load_defaults`: preference defaults depending on the Solidus version**

Solidus 3.1 brings a new feature where preference defaults can take different
values depending on a specified Solidus version. It makes it possible to stop
deprecating old defaults every time we introduce a change in the recommended
value for a setting. After all, they're just that; recommendations. Instead,
now users can explicitly ask for a given Solidus version defaults and, as
before, override the preferences they want.

When upgrading to 3.1, you have to take action to adopt the new behavior.
You'll need to add `Spree.load_defaults('3.1')` on the very top of your
`spree.rb` initializer. As we're not changing any preference default on this
release, nothing will break. A warning will be emitted on boot-up until you do
it!

However, bumping the version given to `load_defaults` straight away for future
upgrades will not be a safe option. Instead, you'll have to go through the new
update process detailed below.

Take a look at [#4064](https://github.com/solidusio/solidus/pull/4064) for more information.

**New update process**

As aforementioned, preference defaults can change after a Solidus release. Once
you have your defaults locked to the current Solidus version, a new upgrade
won't break your application because of them. However, it's a good idea to
adapt your application to the updated recommended settings. To help with this
process, Solidus comes with a generator that you can execute like this:

```bash
bin/rails g solidus:update
```

That generator will create a new initializer called `new_solidus_defaults.rb`,
which will preview all the defaults that have changed between versions, each on
a commented line. From that point, you can activate the new defaults one by one
and adapt your application incrementally. Once you're done with all of them,
you can bump the version given to `Spree.load_defaults` in the `spree.rb`
initializer and remove the `new_solidus_defaults.rb` initializer altogether.

You can read in more detail about [this process on our
guides](https://guides.solidus.io/getting-started/upgrading-solidus#updating-preferences).

On [#4087](https://github.com/solidusio/solidus/pull/4087) you can find more.

**Other important changes**

`Spree::Price#amount` field can no longer be `nil`. Besides adding the
validation at the model layer, we ship with a task that will remove records
where the amount is `NULL` in the database. You should run the task before
executing the new migrations:

```ruby
bin/rails solidus:delete_prices_with_nil_amount
bin/rails railties:install:migrations
bin/rails db:migrate
```

If you're running migrations automatically on deploy, you should run the task
before rolling out the new code. In that case, you first should make sure that
you have affected records:

```ruby
Spree::Price.where(amount: nil).any?
```

If the above code returns `false`, you don't need to do anything else.
Otherwise, copy [the
task](https://github.com/solidusio/solidus/blob/master/core/lib/tasks/solidus/delete_prices_with_nil_amount.rake)
into your code, and deploy & execute it. Another option is to execute it
manually in your console in production. However, be extremely careful when
doing that!! :warning: :warning: :warning:

```ruby
Spree::Price.where(amount: nil).delete_all
```

Take a look at PR [#3987](https://github.com/solidusio/solidus/pull/3987) for more details.

### Other Changes

But there's also a lot of other stuff in this release! If you want to see the full list of the
changes made, plase take a look at the project's [CHANGELOG on GitHub](https://github.com/solidusio/solidus/blob/master/CHANGELOG.md).


We've just released Solidus v3.1.0! Thanks to all contributors, testers, and users who made this release possible. This version's support will end in 18 months: 2023-03-10.

Solidus v3.1

Hello everyone, and welcome to This Month in Solidus: May 2021 edition!

### Solidus <-> ShipStation 1.0.0 Is Out!

After extensive production testing, we're finally happy to release the first stable version of
[solidus_shipstation](https://github.com/solidusio-contrib/solidus_shipstation)!

Our ShipStation integration supports both the legacy XML integration as well as the new, more
powerful ShipStation API. It uses a smart batch-syncing mechanism to work around ShipStation's low
rate limits, which allows it to sync up to 4000 orders/minute via the API, and it supports webhooks
to sync tracking information back to Solidus.

We've been using the extension in production in a few different stores with great success, so feel
free to go ahead and give it a try!

_Pro-tip: Combine solidus_shipstation with [solidus_easypost](https://github.com/solidusio-contrib/solidus_easypost)
to gain complete ownership of your post-purchase experience and fulfillment process!_

### Solidus Now Supports Ruby 3

We have recently introduced [Ruby 3 support!](https://github.com/solidusio/solidus/pull/4072)

While this was a pretty low-lift initiative on our side, it enables all Solidus users to benefit
from all the latest improvements to the language, and paves the way for a more modern Solidus
ecosystem!

### A Goodie for Docker Fans...

If you like developing with Docker and missed Docker support in Solidus, cry no more! You can now
boot up the codebase with as little as `docker-compose up`, thanks to our new 
[Docker Compose support](https://github.com/solidusio/solidus/pull/3947).

We hope this will make it even easier to contribute to Solidus for new and experienced users alike!

### ...And a Few More for Everyone Else!

The community has also been hard at work on a few improvements and bugfixes:

- Stock location sorting had been inadvertently broken in a previous change, but Ikraam Ghoor from
  Nebulab was kind enough to [fix it!](https://github.com/solidusio/solidus/pull/3954) Thanks, Ikraam!
- The [ItemTotal](https://github.com/solidusio/solidus/pull/3431) promo rule is now easier to extend
  and customize, thanks to Elia Schito from Nebulab!
- API attributes have been [moved to a configuration option](https://github.com/solidusio/solidus/pull/4039),
  which makes it easier to customize them without running into any autoloading issues. Thanks to
  Stefano Nada from Nebulab!
- In rare cases, it was possible for two store credit instances to have the same authorization code,
  if they were generated at very close moments in time. This was [fixed](https://github.com/solidusio/solidus/pull/4060)
  by Andrea Longhi from Nebulab!
- A validation on customer returns would break when the return did not have any items. [This isn't the
  case anymore](https://github.com/solidusio/solidus/pull/4068), thanks to Willian Veiga!
- A bug was preventing admins from setting the reason for return items. The issue was found and 
  [fixed](https://github.com/solidusio/solidus/pull/4080) by Andrea Longhi from Nebulab!

That's it for this month! We'll see you in 30 day, stronger, faster and with more updates!

_Spend an awesome Tuesday! 👋️_

Dive in and see everything that happened in the Solidus world in May 2021!

The Solidus Blog

Solidus v3.2

Solidus Quarterly Roundup: Q2 2022

Getting Started with Solidus Starter Frontend

New Solidus releases to address a security vulnerability

Add Venmo To Your Solidus Store

Using Afterpay with Solidus

New Solidus releases to address a security vulnerability

New Solidus releases to address a security vulnerability

Announcing Solidus Conf 7

New solidus_auth_devise & Solidus releases to address a severe security vulnerability

Solidus v3.1

This Month in Solidus: May 2021