panariga/shopify_proxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

first commit

Browse Source
This commit is contained in:
O K
2026-05-26 10:58:49 +03:00
parent c92aee86a2
commit 93ab7e060d
20 changed files with 792 additions and 2240 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
shopify_groundings.md Normal file
View File

@@ -0,0 +1,15 @@
# Shopify App Scopes Justification
This document outlines the business justification for the requested access scopes, which are required to ensure compliance with Ukrainian fiscal and tax legislation.
## 1. `read_orders` (including access to orders older than 60 days)
**Justification:**
Our application assists merchants in complying with mandatory Ukrainian tax laws, which require the generation, printing, and storage of fiscal receipts for all transactions. According to local regulations, tax audits can be conducted for periods exceeding 3 years. Therefore, merchants must have uninterrupted, ongoing access to historical fiscal receipts for all their past orders. We require the `read_orders` scope (including access to all orders, regardless of the 60-day limit) so that the application can retrieve and display historical fiscal documents for the merchant during tax inspections or upon demand, independent of their current acquiring relationships.
## 2. `write_orders`
**Justification:**
To ensure that fiscal documents are permanently and securely accessible to the merchant, our application stores the generated fiscal receipts directly within the order's metafields. This guarantees that the fiscal data is tied to the order in Shopify and remains available even if the merchant terminates their relationship with a specific payment gateway. Since standard payment gateway integrations do not have the required access levels to write this specific data to order metafields, our application requires the `write_orders` scope to save these fiscal receipts and related metadata to the corresponding orders.
## 3. `customer_read_orders` (Access to Customer Order History)
**Justification:**
Ukrainian legislation also strictly requires that the buyer (customer) receives and has access to their fiscal receipt. Our application displays these fiscal receipts directly to the customer via Customer Account and Checkout UI extensions. The `customer_read_orders` scope is essential to allow the application to read the customer's order history within their personal account, fetch the associated fiscal receipts from the order metafields, and display them securely and conveniently to the buyer.