Xinzhi ERP Installation Guide

Prior approval required. Access requires an account provisioned and authorized by Xinzhi staff. This applies to every user and business, without exception. Self-service registration is not available. Installing or authorizing the Shopify app does not grant system access. Contact support@xzkj.ai for account provisioning and access approval; never send passwords or tokens.

One Xinzhi ERP Shopify installation connects ERP operations and an independent customer service workbench. They share the store installation and Connector, but each workspace checks its own business permissions and store access.

For review, use your own Shopify development store and separate synthetic, disposable records. One approved ERP account and enterprise code are supplied in the restricted review instructions; customer service uses that same account. No advance store-domain registration or store whitelist is required. Never send passwords, access tokens or customer payment information to support.

On this page

1. Install and link your account

  1. Start with Xinzhi ERP's installation entry on Shopify. Before the app is published, use the Shopify-owned review installation link supplied in the restricted test instructions. Choose your own development store and approve the requested permission groups. Do not manually enter a shop domain.
  2. After Shopify authorization, open the app in Shopify Admin. If it says Shopify authorized · ERP linking pending, select Link an existing ERP account. Sign in with the staff-provisioned ERP enterprise code, email and password. Review the Shopify store and target ERP business, then select Authorize and connect. The approved account needs shop authorization permission; it does not need tenant-administrator access. A newly authorized store is created in that business and assigned only to the linking account. An existing ERP store can be linked only when already assigned to that account. No enterprise, user or unrelated shop permission is created by installation.
  3. Return to Shopify Admin App Home and confirm that the connection is ready. In ERP, open Stores / 店铺 to confirm that this store is authorized and visible to the linking account. A pending link alone does not grant ERP business access. If the ERP session expires, sign in as the same approved account and retry this link; do not switch businesses or claim an existing unassigned shop.
  4. Open the app in Shopify Admin and verify the documented installation, account linking, configuration and connection-management workflow. A connection-status page alone is not the complete embedded business experience. Independent ERP operations and continuously monitored customer conversations may use their own workspaces; external links alone do not prove that the required in-Admin setup and management work. Stop a blocked scenario and contact support.
  5. In the ERP Store List, verify that your store is Authorized and that the submitted scope checklist is complete. Reopen the app in Shopify Admin to confirm its connection. Use the same store throughout the ERP and customer-service scenarios; stop and contact support if authorization or setup is incomplete.

ERP and customer service share the existing ERP account. Select Customer service in ERP to enter without another password. At the direct workbench URL, enter the same ERP enterprise code, account and password to sign in without leaving the page. Each business retains separate sessions and permission checks. Direct-login passwords are transiently relayed to ERP, not stored as customer-service credentials; ERP bearer tokens are not returned to the customer-service browser. Matching emails do not link identities.

2. Review ERP workflows

Complete the matching scenario before claiming a requested scope works. Check the displayed before/after values and Shopify's result; an empty list or a successful login is not proof of a business action.

  1. Products: in ERP, open Products > Online product matching > Preview Shopify products, select your store and refresh the preview (read_products). This is read-only. For an import test on your own development store, create a synthetic Shopify variant with SKU SKU-HOSTED-1, an existing active ERP inventory SKU. Refresh the preview, select its exact match, choose Import to ERP, then confirm the saved listing in Online product matching. Only exact SKU matches are importable; unmatched variants remain preview-only. This does not change Shopify products, prices or inventory.
  2. Customers: find the synthetic customer's recent-order relationship (read_customers). This read does not edit Shopify customer profiles.
  3. Current orders: preview a synthetic Shopify order and select an active warehouse visible to your ERP account before importing it. If only one warehouse is assigned, ERP selects it automatically. Import writes ERP-local records only. Use a separate eligible disposable order for an explicitly confirmed address update or cancellation (write_orders).
  4. Historical orders: select the older-than-60-days mode and preview an order that actually meets that cutoff before importing it into an assigned warehouse (read_all_orders). If the store has no qualifying test order or approval is missing, this scenario remains unverified; do not change local dates to simulate it.
  5. Order edits: on a separate unfulfilled order, review and confirm a quantity, mapped-line or discount change (write_order_edits). Do not reuse an order after fulfillment has begun.
  6. Inventory: inspect the location-to-warehouse mapping (read_locations), compare ERP and Shopify quantities, then confirm one prepared publication (write_inventory).
  7. Fulfillment: inspect the prepared package, merchant-managed location, quantities and test tracking details, then confirm shipment publication (write_merchant_managed_fulfillment_orders). This does not buy a shipping label or act as a third-party fulfillment service.
  8. Returns and refunds: approve the eligible prepared return, review Shopify's calculated refund preview and explicitly confirm the operation (write_returns). Do not substitute a hand-entered refund amount.
  9. Disputes: review the prepared test-dispute status, amount, reason, related order and processing deadline (read_shopify_payments_disputes). Xinzhi ERP does not read, edit, upload or submit dispute evidence; merchants handle evidence in Shopify Admin.

3. Enable storefront support

  1. In Shopify Admin > Apps > Xinzhi ERP, find Xinzhi Chat and select Check status. Store configuration ready confirms this store's chat service configuration; plugin detection is advisory. A mismatch or unavailable result leaves setup links locked; contact support rather than changing enterprise IDs or destinations manually. This check does not validate customer-service credentials or agent assignments.
  2. Wait for the new store's customer-service setup to finish. In ERP select Customer service to open the workbench without another password. Direct workbench access accepts the same ERP enterprise code, account and password on-page. Verify the correct enterprise and newly connected store; this does not request a second Shopify authorization or grant other employees access.
  3. Open the store's Shopify channel. Confirm that authorization belongs to the shared Xinzhi ERP application and that the customer-service source is bound. A pending or failed setup is not a successful chat test; retain the displayed message and contact support.
  4. From App Home select Open theme editor. Alternatively, the customer-service Shopify channel's Copy plugin enable link copies the official deep link for manual use in the matching store's browser. The copy action never opens, switches, or controls a browser. No automatic browser navigation or read_themes permission is required.
  5. Enable Support Chat under Xinzhi ERP in App embeds and save the theme you will test. Return to App Home and check again. Theme detection is advisory and covers only the published theme; a detected embed is not proof that its toggle was saved or that messaging works.
  6. Preview the storefront manually, open the widget and send a clearly synthetic visitor message. Theme-specific appearance and featured products are managed in Shopify's theme editor; conversation operations stay in customer service.

4. Complete a support conversation

  1. On the storefront, complete the displayed customer sign-in using a test email you control, then send a synthetic message from the selected store.
  2. In the customer service workbench, find that store and conversation, claim the conversation if it is unassigned, and reply.
  3. Return to the storefront and verify that the widget receives the reply. Refresh the workbench and confirm that the conversation remains accessible.

Provide one verified ERP reviewer account with the permissions needed for the submitted scenarios and the selected test store. ERP session tokens are rejected as customer-service sessions: entry uses a short-lived, single-use proof and a separate customer-service session. An ERP-only account does not receive customer-service access automatically. A role name or Shopify scope list alone does not prove this isolation.

5. Disable, uninstall and reinstall

  1. Disable the app embed in the tested theme, save and verify that the storefront widget disappears. This does not uninstall the app.
  2. Uninstall the single Xinzhi ERP application from Shopify Admin. Verify that ERP Shopify access and the customer-service Shopify relationship stop; uninstall must not leave an active Shopify credential.
  3. Reinstall from Shopify, complete authorization again, and use the same approved ERP account to restore the existing assigned store connection. Confirm that no duplicate ERP store record is created. Recheck the channel and any theme enablement needed before resuming chat.

Uninstall revokes access; it is not proof that all stored operational records have been deleted. Follow the Data Access and Deletion process for verified data requests. Never run a whole-store redaction test on a shared review store.

6. Troubleshooting and safe recovery

Reviewer help: support@xzkj.ai. Include the workflow, test store domain and approximate time, without credentials or customer data.