Description

Order interoperability needs to be implemented in strapi-bpp. This will allow for seamless integration and communication between different systems.

Goals

• Understand the requirements for order interoperability
• Design the implementation strategy
• Implement order interoperability in strapi-bpp

Expected Outcome

Order interoperability is successfully implemented in strapi-bpp and is working as expected.

Acceptance Criteria

• The implementation meets the requirements for order interoperability
• The implementation passes all relevant tests
• The implementation does not introduce any new issues or bugs

Mockups / Wireframes

Product Name

Beckn

Domain

strapi-bpp

Tech Skills Needed

Backend Engineering

Complexity

Medium

Category

Interoperability in strapi-bpp

Sub Category

Implement order

We have a few non-Beckn APIs that are primarily used on the Buyer side app by the UI. The primary among this is the Strapi backend on BAP which takes care of user login, profile and history. This issue is not about that.
Apart from Strapi backend, there are a few smaller backends that provide one/two endpoints each. They are
a. ChatGPT bridge used as link between tourism and retail
b. Telemetry sink
c. Policy Admin
d. Event collector

Instead of having a separate repository for each, move them all into a single repository called as APIHub.

Description

There are multiple small projects with very few APIs that are non-beckon. Listing all the projects that can be merged into a single project will improve the code manageability.

Goals

• List all the non-beckn APIs/projects that can be clubbed into a single project.

Expected Outcome

List of APIs that can be merged in a single project.

Acceptance Criteria

• List of projects/APIs to be merged in single project.

Implementation Details

NA

Mockups / Wireframes

[Include links to any visual aids, mockups, wireframes, or diagrams that help illustrate what the final product should look like. This is not always necessary, but can be very helpful in many cases.]

---

[Please note that the below section of the ticket has to be in the format as mentioned as it is key to enabling proper listing of the project. Please only choose the options mentioned under the headings wherever applicable.]

Tech Skills Needed:

NA

Complexity

Low

Category

Analysis

Sub Category

Analysis