Sitoo 中断历史

We have identified an issue with Infrasec who handles the Control Unit for a few of our customers operating in Sweden. Until then you unfortunately will have to charge the customers outside of the Sitoo POS app (for instance with cash or a Swish number) and write a physical receipt. NOTE! This in only relevant for our customers operating in Sweden and dependent upon the Control Unit provided by Infrasec.

Infrasec are now up and running so the operation should be normal again.

We’re investigating a disruption affecting the ability to log in to the New Back Office. We will provide more info continuously.

We have identified the issue and are working on a fix.

A fix has been deployed that addresses the issue. We will continue to monitor the service.

This incident has been resolved.

We are currently investigating an issue affecting a small number of customers, where multiple items (usually two) are added to the shopping cart despite scanning the product only once. This issue has been identified in version 1.4.42 and later. We’ll provide further updates as soon as more information becomes available.

We have identified several potential issues and are finalizing fixes for them right now

We've deployed an internal beta that addresses the issue. We'll continue monitoring performance and plan to release a public beta tomorrow

We've deployed a publuc beta. We'll continue to monitoring performance.

The issue persists in the public beta. We’re actively analyzing new data and logs to isolate the remaining problem.

After analyzing additional logs and data from affected devices we identified the potential issues. We’ve just released a new public beta with a fix addressing this issue. We'll continue to monitoring performance.

We can confirm that the issue with double scanning has not reoccurred since applying the latest patch release for Sitoo POS Beta 1.4.43 (221) A production release will be available soon.

Sitoo POS Android version 1.4.43 (85) is now available to download and fixes the issue with double scanning. We'll continue to monitoring performance

We're currently investigating two related issues affecting Z reports: 1) Z report number series are restarting from 1 unexpectedly (starting from version 1.91). 2) Users who closed Z reports last night may receive prompts to close again, causing the number series and grand totals to reset. Note: Journal data remains accurate. This issue only impacts the Z report numbering. The 3 grand total fields in the journal data are also affected, as they reflect the information on the Z reports (moneygrandtotalsales, moneygrandtotalrefund, moneygrandtotalnet) We strongly reccomend not to upgrade from version 1.90 until a fix is released

The root cause has been identified, and we are working on a fix.

We are actively working on resolving the issue and will continue to provide updates as soon as more information becomes available.

Version 1.93 is now available in the App Store with the following fixes: • CRM V2 – Customer Addition to Cart Resolved an issue preventing customers from being added to the cart when the CRM V2 SPI did not return customer transactions. • Z-Report Numbering Fixed a bug causing the Z-report ID numbering to reset to 1 instead of continuing sequentially. We will continue monitoring this closely and provide updates as needed.

This incident has been resolved with the new version 1.93. We will continue to monitor the status.

We are currently experiencing an issue affecting split payments when using Adyen as the payment method. When attempting to make a partial payment through Adyen.

We have identified that the issue specifically affects iOS version 1.91. We recommend not installing or upgrading to version 1.91. We are working to fix this issue. Only a small number of customers are affected.

POS iOS version 1.92 has been released with a fix for this issue. The update has been pushed to the AppStore and should be available shortly for download.

We are continuing to monitor for any further issues.

This incident has been resolved with the new version 1.92. We will continue to monitor the status.

We are currently experiencing issues with the latest version 1.86 of the POS App (iOS) regarding down payments. We currently don't recommend customers to update to version 1.86. Thank you for your patience.

We are still investigating. The issue affects customers using payment methods Down payments and Invoice that has upgraded to version 1.86 on iOS (iPad and iPhone). Note: Directly after a Commit of a booking/order an error message will be shown. The booking/order will still be created but in the same time also Cancelled in Sitoo. The product will still be in the cart. How this affects you as a customer is unique per customer depending on each customers own implementation to other systems.

Current status: - We have identified the issue and are working with a new release. - The problem occurs in relation to Down Payments and Invoice as payment methods immediately after committing a booking/order, where an error message appears. - The booking/order is still created but is simultaneously canceled in Sitoo. The product remains in the cart. - We are also investigating an issue related to migrating the journal to the new service. - The impact of this issue may vary depending on your specific system implementation. Recommended Action: If you have not yet updated to version 1.86, we strongly recommend postponing the update until hotfix 1.87 is released. If you have successfully updated to version 1.86, no action is required. If you have any questions, please don’t hesitate to reach out to our support team. We appreciate your patience and will keep you informed as we work towards a resolution.

A fix has been implemented, and version 1.87 is now available on the App Store. The new release resolves the issue with Down Payments and Invoices and addresses the error relating to the migrating error to the new journal service that affected a handful of devices.

Customers who have updated to version 1.87 report that the update has successfully resolved the previously identified issues. Recommended Action: In general we recommend updating to version 1.87, especially if you're currently using version 1.86 and encountering problems with Down Payments or Invoices as payment methods.

We have identified a potential issue with Infrasec who handles the Control Unit for a few of our customers operating in Sweden. Until then you unfortunately will have to charge the customers outside of the Sitoo POS app (for instance with cash or a Swish number) and write a physical receipt. NOTE! This in only relevant for our customers operating in Sweden and dependent upon the Control Unit provided by Infrasec.

A fix has been implemented and we are monitoring the results.

The implemented fix was successful. Operations back to normal.

We are currently experiencing issues with the POS App running on devices with Android Version 14 due to a recently found bug related to taxfree receipts being printed with a LARGE font. Sitoo currently does not recommend upgrading Android devices to Android 14 (API level 34) until a bug fix has been released. Thank you for your patience.

The latest release of Sitoo POS on Android (1.4.34) contains a fix for this issue.

Voyado, who is a CRM used by several Sitoo customers have an ongoing incident. For direct status please see: https://status.voyado.com/

Voyado reports that the incident has been resolved.

We are currently investigating a reported issue with the POS App for Android affecting one customer in several stores. The POS App has slow response times in the interface for store staff (up to several seconds) when performing for example scanning of products. We are investigating. Thank you for your patience.

We are still investigating in close cooperation with the affected customer. Some mitigating changes has been put in place and is under monitoring.

Mitigating actions had a verified effect.

We are currently experiencing issues with the switchboard for Sitoo Support. Our provider has been notified and is working on it. Sitoo international support it still reachable at +46 8 5000 9390.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

We are continuing to monitor for any further issues.

This incident has been resolved.

We are currently experiencing issues with the switchboard for Sitoo Support. Our provider has been notified and is working on it. Sitoo Support is still reachable at: https://support.sitoo.com/hc/en-us/requests/new.

We are continuing to investigate this issue.

This incident has been resolved.

Infrasec, who handles the Control Unit is currently having a service disruption. They are actively troubleshooting the problem and hope to solve it as soon as possible. Until then you unfortunately will have to charge the customers outside of the Sitoo POS app (for instance with cash or a Swish number) and write a physical receipt. Infrasec are currently moving over operations to their secondary data center. https://status-io.infrasec.se/

Note! Only Swedish customers that are using a control unit are affected.

Infrasec are now fully up and running on their secondary site so the operation should be normal again.

Infrasec, who handles the Control Unit is currently having a service disruption. They are actively troubleshooting the problem and hope to solve it as soon as possible. Until then you unfortunately will have to charge the customers outside of the Sitoo POS app (for instance with cash or a Swish number) and write a physical receipt.

Infrasec has now updated its status page. See: https://status-io.infrasec.se

Infrasec is working on this issue with all resources available to solve this issue ASAP.

Unfortunately, we have no new information from Infrasec and there's nothing we can do at this point. We apologize for the inconvenience.

Latest news from Infrasec is that the problem is solved. We are still monitoring this.

Infrasec has confirmed that the issue has been resolved. Back to normal since 15:55 (CET).

The webhooks service is queueing up events and only a few are delivered to the destination. This causes events to have a delay before being delivered. We are currently investigating this issue together with AWS.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

Events have been dispatched. Queue back to zero. Issue has been resolved.

There is currently issues with Fiskaly (the compliance in Germany). We are monitoring this closely, you can follow the statuses here https://status.fiskaly.com

We are continuing to monitor for any further issues.

Fiskaly services are up and running again. Problem solved.

This incident has been resolved.

We have identified an issue when using Sitoo POS. We will provide an update as soon as it becomes available.

We are continuing to investigate this issue.

We had a minor incident related to an incomplete sync to Sitoo POS. If you still experience problems logging in to Sitoo POS... Please log in to your BackOffice and change the PIN of one of your contacts (whichever). Wait a few minutes and it should work. Are you in Sitoo POS, but can not make payments, searches, etc... Go to "Menu" > "Settings" > "Advanced" > "Clear cache".

This incident has been resolved.

Infrasec, who handles the Control Unit is currently having a service disruption. They are actively troubleshooting the problem and hope to solve it as soon as possible. Until then you unfortunately will have to charge the customers outside of the Sitoo POS app (for instance with cash or a Swish number) and write a physical receipt.

We are continuing to investigate this issue.

Infrasec has now updated its certificate and it should work again.

We are awaiting confirmation from Infrasec that the issue has been resolved.

Infrasec has confirmed that the issue has been resolved. Back to normal since 18:39 CET.