# Roadmap

Use this page to check whether a feature you need is coming, and to [ask for one that isn't](#request-or-vote). Before you ask, check what's [already in WCPOS](#already-shipped). The roadmap board on GitHub always has the current status.

## Check the live roadmap[​](#the-public-roadmap "Check the live roadmap으로 직접 링크")

The board shows what is in progress, what is up next, what is planned for later and the ideas not yet planned.

[WCPOS Roadmap on GitHubIn progress, up next and later, updated as the work moves.](https://github.com/orgs/wcpos/projects/4)

Direction, not dates

The roadmap shows what we plan to build next, not a promise of when, and the order can change. What many stores ask for moves up, so if a feature matters to your store, [tell us](#request-or-vote).

## What's coming after 2.0[​](#what-were-working-on "What's coming after 2.0으로 직접 링크")

The next three releases each have one theme. They are planned in this order:

* [2.1: Fiscal compliance](#fiscal-compliance)
* [2.2: Control what each cashier can do](#cashier-permissions)
* [2.3: Works with your other plugins](#your-other-plugins)

Looking for one feature? Find it in the table and tap its name.

| Feature                                                                                                      | Planned for                 |
| ------------------------------------------------------------------------------------------------------------ | --------------------------- |
| [Records the law requires (France, Spain)](#records-the-law-requires)                                        | [2.1](#fiscal-compliance)   |
| [Report templates for the Z-report and shift summaries](#report-templates)                                   | [2.1](#fiscal-compliance)   |
| [Scale barcodes](#scale-barcodes)                                                                            | [2.1](#fiscal-compliance)   |
| [Exchanges](#exchanges)                                                                                      | [2.1](#fiscal-compliance)   |
| [Card payments offline on SumUp readers](#card-payments-offline)                                             | [2.1](#fiscal-compliance)   |
| [Limit what each cashier can do](#permissions-by-role)                                                       | [2.2](#cashier-permissions) |
| [Shared till settings for all cashiers](#shared-till-settings)                                               | [2.2](#cashier-permissions) |
| [Loyalty points, gift cards, subscriptions](#loyalty-gift-cards-subscriptions)                               | [2.3](#your-other-plugins)  |
| [Pricing rules and email lists](#pricing-rules-email-lists)                                                  | [2.3](#your-other-plugins)  |
| [Product Add-Ons, Bundles, Composite Products, Bookings, Product Options, Product Vendors](#more-extensions) | [2.3](#your-other-plugins)  |
| [Alerts for new online orders](#order-notifications)                                                         | [2.3](#your-other-plugins)  |
| [Email templates for POS orders](#later)                                                                     | [Not yet planned](#later)   |

### 2.1: Fiscal compliance[​](#fiscal-compliance "2.1: Fiscal compliance으로 직접 링크")

The theme is for stores in countries whose law requires the till to prove that no sale was altered. The release also carries four other changes.

* **Records the law requires**: the POS keeps records that show whether a sale was changed. France and Spain come first.

  What fiscal compliance covers

  Signed records, numbering with no gaps, official closure reports, an audit file to export and, where the country demands it, reporting to the tax authority from the POS. France's rules are NF525 and Spain's are VeriFactu. 2.0 laid the groundwork; see [Receipts and refunds built for fiscal rules](/ko/releases/whats-new.md#receipts-and-refunds).

* **Report templates**: choose the layout of the end-of-day report (the Z-report) and of shift summaries, and print them on A4 or thermal paper.

* **Scale barcodes**: scan a barcode printed by a weighing scale, and the POS adds the product at the price or weight in the barcode.

* **Exchanges**: take a return and sell the replacement in one transaction.

* **Card payments offline**: planned for 2.1 on SumUp's Solo and Solo Lite. SumUp must also switch it on for your account. Until then, a card reader paired with the till needs a connection. To see what already works with no connection, read [Offline Mode](/ko/sell/offline-mode.md).

  Which readers, and how an offline card payment works

  The Solo and Solo Lite connect to the POS app over Bluetooth. While the POS is offline, the reader approves the payment provisionally and sends it when the connection returns. SumUp can still decline it then, and your store carries that risk.

### 2.2: Control what each cashier can do[​](#cashier-permissions "2.2: Control what each cashier can do으로 직접 링크")

Today you can already choose, per role, who may open, count, close and approve the register, and who may open the **Reports** screen and see the expected cash; see [Accessing the POS](/ko/manage-store/staff-permissions.md). Most other till actions are open to every cashier. 2.2 adds control over them.

* **Permissions by role**: decide which roles may give refunds and discounts, change a line's price, void or reopen orders and see other cashiers' sales.

  Which pages you can hide, and what changes by default

  You can also hide the **Orders**, **Customers** and POS settings pages from a role. A control a cashier may not use is hidden or locked. Every permission starts switched on, so nothing changes in your store until you turn one off.

* **Till settings for the whole store**: set a till setting once for every cashier, such as whether the receipt opens after checkout, and decide which ones a cashier may still change.

### 2.3: Works with your other plugins[​](#your-other-plugins "2.3: Works with your other plugins으로 직접 링크")

The WooCommerce plugins your online store runs, working at the counter.

* **Loyalty, gift cards and subscriptions**: earn and spend points, sell and redeem gift cards and store credit, and start a subscription at the till.
* **Pricing rules and email lists**: a bulk price or discount rule applies at the till as it does online, and an email taken at the counter joins the same mailing list.
* **More WooCommerce extensions**: Product Add-Ons, Product Bundles, Composite Products, Bookings, Product Options and Product Vendors.
* **Order notifications**: an alert with sound at the till when a new online order comes in, which stays until someone acknowledges it. Made for restaurants, where an order needs attention at once.

### Not yet planned[​](#later "Not yet planned으로 직접 링크")

Ideas with no release yet are on the board too, for example email templates for POS orders that differ from your online order emails. If one of them matters to your store, [ask](#request-or-vote).

## Already in WCPOS[​](#already-shipped "Already in WCPOS으로 직접 링크")

### Included in 2.0[​](#shipped-in-2-0 "Included in 2.0으로 직접 링크")

2.0 rebuilds the register and its checkout. You can split a payment between cash and cards; take cash, a card on your own terminal or another payment recorded at the till with no connection, on a sale your store already has; open the register with a float and close it with a count; send the amount to a card reader from the till; and show the customer their cart on a second screen. Card readers and the second screen come with Pro. Read [What's new in 2.0](/ko/releases/whats-new.md) for the full list.

### Often asked for, already here[​](#often-asked-for "Often asked for, already here으로 직접 링크")

Before you ask for a feature, check that it isn't here already:

[Prevent oversellingStop a sale of stock you don't have, in the cart and again at checkout.](/ko/settings/checkout.md#prevent-overselling)

[Coupons at the tillSearch for coupons, apply them and use more than one in a sale.](/ko/manage-store/coupons.md)

[RefundsRefund all or part of an order, to the original payment method or as cash from the till.](/ko/manage-store/orders/refund-rules.md)

[Cloud printingPrint receipts to printers that aren't attached to the till.](/ko/hardware/receipt-printers/cloud-printing.md)

[Thermal receiptsDesign receipt layouts for Epson and Star thermal printers.](/ko/settings/receipt-templates/thermal-templates.md)

[Store healthSync speed, server load, what has downloaded, and the activity log.](/ko/troubleshooting/store-health.md)

[How syncing worksFor developers: how the POS keeps your store's data in step and sends back changes made offline.](/ko/developers/sync-engine.md)

## Ask for a feature[​](#request-or-vote "Ask for a feature으로 직접 링크")

The features many stores ask for move up the roadmap. Ask in one of two places:

* **[Discord](https://wcpos.com/discord)**: the quickest way to reach us and other store owners. Post in `#forum` for a feature request, or `#general` for a quick question.
* **[GitHub Discussions](https://github.com/orgs/wcpos/discussions)**: propose a feature, or add your use case to one someone has already proposed. Many roadmap items started as a discussion.

Say what you're trying to do

Tell us the job, not only the feature name: what happens at your counter today, and what you want to happen instead. A real example shapes the design more than a vote.

## Related Documentation[​](#related-documentation "Related Documentation으로 직접 링크")

[What's new in 2.0Everything that changed in the 2.0 release.](/ko/releases/whats-new.md)

[Offline ModeWhat works with no connection, and what waits for one.](/ko/sell/offline-mode.md)

[Free vs ProWhich features come with WCPOS Pro.](/ko/getting-started/free-vs-pro.md)