We’re gradually rolling out support for one time checkouts via Firmhouse Checkout. We invite all our merchants who are interested to get in touch and join our private beta.

Adding one time checkouts allows Firmhouse to support more traditional e-commerce in combination with all the new and innovative models we support such as subscriptions, rental, and try & buy. Adding better support for one time checkouts is a key point for making sure you as merchant can offer a consistent and holistic experience to all your customers. Whichever way you choose to sell.

With one time purchases enabled:

• Checkouts with only “one off” products in the cart will be marked as “one time purchase” instead of being a subscription. Full subscription carts or hybrid cards will still be treated as subscriptions.
• Analytics and insights will ignore one time purchases from subscription metrics, making it easier to distinguish between your one time revenue and your recurring revenue.
• The Self Service Center will be updated to make a clearer distinction between one time orders and subscriptions.

We're ramping up to release some nice smaller updates over the course of the next few weeks. For this week, we would like to introduce Audit Logs for Enterprise Tenants and a few minor other improvements.

🔏 Audit logs for Enterprise tenants

We now support audit logs for tracking security-related events such as user logins/logouts, data access, API token generation, and batch exporting of data.

Audit logs are securely stored in WorkOS and can be browsed and searched via the Firmhouse portal or exported to CSV. There is also an option to set up log streaming to any of the supported SIEM systems, like Amazon S3, DataDog, and Splunk.

Tenant team members that have the appropriate access rights to Audit Logs can access audit logs from the account menu after being logged in to their Enterprise tenant.

Other improvements and fixes

• We now show the date of birth in iDin identification details.
• Added option to skip cancellation email when cancelling via API.
• Fixed validation message on creating a subscription via API when a required extra field is missing.

EU B2B 0% reverse taxes

You can now set up a Tax Rate for your plans and products in services when you sell to businesses cross-Europe. That way you can charge the local VAT when shipping to customers in your own country. Customers from all other countries will get a 0% reverse tax on invoices.

Prevent charging non-paying customers

You can now choose to skip charging customers that are already marked as non-paying. With this setting enabled we will still invoice customers for your services. However, when they are marked as non-paying we will not attempt to charge the customer via your configured payment service provider.

This way you can prevent incurring expensive PSP chargeback fees. Especially with customers using SEPA as their payment method.

Native date of birth field on Checkout

You can now enable a Date of Birth field as a native Checkout field. The field is hidden by default and you can enable it in your project’s Checkout preferences. The advantage of using this new native field over using an Extra Field is that we can also send this field to any acceptance check or risk score rating services automatically.

Other improvements & bugfixes

• Improved export and report generation times.
• Store payment method summary from PSP.
• Fix that finance team members couldn't refund payments.
• Expose "supplier" on Product type in API.
• Send new native Date of Birth field to Focum acceptance checks.
• Cache of Customers overview not always cleared when cancelling subscriptions.
• Fix not attempting to fetch price from Shopify when product is not linked to Shopify.

In November we've spent a good time adding and updating documentation for setting up and integrating Firmhouse. Apart from this we're working on some exciting features and are making fixes & improvements on a daily basis.

Webhook and Liquid template tags documentation

We've written documentation on which Liquid template tags you can use in your email templates and webhook payload templates.

Head over to https://developer.firmhouse.com/liquid to have a look.

Developer Community

We've kicked off work on our developer community and knowledge-base. We'll be filling it up with more raw tips, tricks, and code samples to make your life in integrating Firmhouse onto your store and other systems easier.

Head over to https://devcommunity.firmhouse.com to find common questions and answers.

Fixes and improvements

• Updated Shopify to latest API and removed deprecation warnings.
• Fixed an issue with linking Firmhouse products to Shopify products.
• Fixed using the right currency in order exports.
• Updated our Storefront JavaScript SDK so that you can now force-set the customer's language.
• Fixed a Intrum reports that would show duplicate invoices.
• Added a Copy button to easily copy the payment link of an invoice.
• Added a new report to export all invoice lines with product information.
• Translated Checkout to Italian.
• Deprecated Payment#status field in GraphQL and updated documentation for new Payment#paymentStatus field.
• Fixed Swedish copy for a manually applied discount on Checkout.
• Made our Checkout and Portal UI more consistent and faster by fully switching to TailwindCSS and dropping Bootstrap.
• Added a shipOrderedProducts mutation to GraphQL which allows developers to generate an order (and if applicable a charge) for given products.
• Fixed a consistency issue on Polish invoice page.
• Exposed currency on the Invoice type in our GraphQL API.
• Fix issuing refunds in a different currency from EUR.
• Added TwinT, Klarna Pay Now, and Klarna Pay Later as available payment method on Adyen.
• Also apply configured address validations on billing address and not just main/shipping address.

We've updated our Shopify integration to the latest Shopify API version. So we're now fully back on track and use Shopify's latest API.

You may have received messages from Shopify that our integration with your store used a deprecated field type and that you had to make sure these were upgraded before January.

So worry no more! We took care of it and everything should again be running smoothly without deprecation warnings.