Operators regularly ask if they can look up what emails were sent to a user and what they contained. Ideally, this would be added to the history. A simple version might only mention what type of email was sent, an improved one would also contain the body specific to that email.

Automatically increase/decrease a unit type's price depending on occupancy. For example: * If a unit type is 90% occupied, automatically increase price by 10% for upcoming bookings. * If a unit type is 30% occupied, automaticaly decrease price by 15% for upcoming bookings. This feature is now live. Read more about how to use [Dynamic pricing here](https://help.storeganise.com/article/340-dynamic-pricing).

In fixed date billing mode, tenants that move in during a month pay rent for the remainder of the current month (month 0) plus for the next month (month 1), e.g., a tenant that moves in on Dec 22 pays for Dec 22 - 31 + Jan 1 - 31. Operators welcome charging the month 1 when tenants book at the end of a month. But when tenants book at the beginning of a month, they often find that only month 0 should be charged. Introduce a cut-off date that allows operators to set the day of the month after which month 1's rent is included in the first invoice, e.g., if the cut-off-date is set to 15 and the tenant books on the 13th, they will only pay month 0, but if a tenant books on the 17th, they would pay month 1, too.

- A flexible tool for setting up tasks & reminders throughout the system - e.g. a reminder to call your customer, conduct maintenance on a unit or any other task that needs to be carried out This feature has now been published. Learn more about [tasks & reminders here](https://help.storeganise.com/article/339-tasks-reminders).

For imported rentals, rental extensions, transfers, or price changes, for many situations an operator would want to update the signed agreement We need to add a new API endpoint and UI button for this in the customer portal

At the moment, lists of invoices, units, rental, etc. can be exported as CSV-files. Opening them in Excel, Google Sheets or Numbers can take a few steps that not everyone is familiar with. For added convenience, add an option to export data as Excel files.

If a customer email fails and we receive an automatic notification we can reach out over the phone or any other contact information to ensure they receive our communications. If the email address changed or is misspelled or any other reason, he/she may be missing regular notifications on business operations, changes in price, overdue payments but also regulatory notifications when they are in default.

Allow tenants to commit to a certain period (e.g. 6 or 12 months) and receive a discount for that commitment. The commitment is NOT a prepayment. Instead, tenants receive a discount by agreeing to commit themselves for a certain period. This feature could reuse elements of the "prepayment" feature, i.e.: - let the operators decide if they want to offer prepayments, commitments, or neither - let the operator define the commitment periods (always 1 month, plus e.g. 6, 12, or others) - for every period, let them define a title, description and promo code that is auto-applied Commitments should be correctly communicated in the booking summary in the customer portal.

Storeganise currently has an `invoice.created` webhook event. In order to better integrate with other accounting systems and Zapier, additional webhooks are required: * `invoice.updated` * `invoice.sent` * `invoice.paid` * `invoice.deleted` Nice to haves: * `invoice.failed` * `invoice.pending` **Edit**: we ended up adding the following events: - `invoice.state.updated` with data: {invoiceId, siteId, from: prevState} - `invoice.payments.updated` with data {invoiceId, siteId} (this is also invoked with deleted payments) - `invoice.deleted` with data: {invoiceId, siteId}

Currently invoicing is run on a monthly basis. Customers can be set to pre-pay for different periods but once that prepayment balance is used up, the billing returns to a monthly schedule. Where customers have committed to paying every 3, 6, 12 months, this function would set this and have the system automatically invoice for the next corresponding period.