Project

General

Profile

Production Ticket(ST) #12001

Express365 - Enquiry on E365 API

Added by Alfred Tan 4 months ago. Updated 3 months ago.

Status:
Ticket Resolved
Priority:
P3 - Medium
Assignee:
Start date:
11/06/2024
Due date:
21/06/2024
% Done:

100%

Estimated time:
Spent time:
Job Remark:
Ticket Logged Date:
11/06/2024
Ticket No.:
Related Ticket ID:
Type:
Support Request
SLA Initial Response:
11/06/2024
SLA Delivery:
13/06/2024
Esclation Time:
Issue Reoccurance#:
Actual Initial Response:
14/06/2024
Resolution:

Problems: Esasy store request E365 have an enhance in API
Step to simulate the problem: check with Principal
Root cause: user enquiry - MCC
Current outcome: waiting feedback from principal
Time spent on: escalate to Principal

Requester ExpectedDeliveryDate:
Delay Justification:
Priority Seq:
Effort (Hour):
External Ticket #:

None

Guidance or help by :
Chongyu

Description

Message to be forwarded to EXPRESS365 IT person

Order customer binding issue
- express 365 API doesnt support
- Every order from EasyStore will show customer name as general terms like " cash sales " or "easystore", can't show customer name ya

Hi Mr Tan, our integration from EASYSTORE need your help to amend the API to ALLOW >>> TO ABLE SHOW CUSTOMER NAME on Every order from EasyStore will show customer name as general terms like " cash sales chan wai wong “ or "easystore - liew june may“
------------------------------

Having two question here
- Will creating sales invoice auto decrease the inventory?
- What API should we called when sales invoice cancelled or refund?
- have the API for sales invoice to call the customer data (contact person)?

History

#1 Updated by Alfred Tan 3 months ago

  • Subject changed from Express365 - Enquiry to Express365 - Enquiry on E365 API
  • Description updated (diff)
  • Status changed from Assigned To to Support In Progress
  • % Done changed from 0 to 40

#2 Updated by Alfred Tan 3 months ago

  • Due date changed from 13/06/2024 to 21/06/2024
  • Status changed from Support In Progress to Escalated to 3rd Party
  • Actual Initial Response set to 14/06/2024
  • Resolution updated (diff)

#3 Updated by Alfred Tan 3 months ago

  • Guidance or help by changed from None to Chongyu

#4 Updated by Alfred Tan 3 months ago

  • Status changed from Escalated to 3rd Party to Ticket Resolved
  • % Done changed from 40 to 100

Also available in: Atom PDF