Data model issue in Fulfillment

[zoyaashik]

Description
During testing across multiple domains, an issue was discovered where item fulfilment details were not populating. Further investigation revealed that the issue stemmed from the fulfilment's relationship configuration. it was found that assigning a fulfilment to a new provider causes its association with the previous provider to vanish due to the current relationship setup.

Goals
The fulfilment details needs to be populated from Strapi for all providers

Expected Outcome
Provider needs to have fulfilment details

Acceptance Criteria
Make Datamodel to accept fulfilment details for all providers

Implementation Details
N/A

Mockups / Wireframes
N/A

---

[Please note that the following section of the ticket must adhere to the specified format as it is crucial for proper project listing. Please select only the options mentioned under the headings where applicable.]

Product Name
Strapi plugin

Project Name
Strapi plugin

Tech Skills Needed:
Strapi

Complexity
Medium

Category
Test

Sub Category
Testing

[zoyaashik]

The existing data model has a "Provider belongs to Many" relationship with fulfilment, which does not allow the same fulfilment to be assigned to multiple providers. Initially, it was suggested to make fulfilment a master table to enable its assignment to various providers, but this approach did not support assigning the same agent to each fulfilment across different providers. To resolve this, it was decided to move the agent ID column from the Fulfilment table to the Item Fulfilment table, linking agents to individual items instead.

CC @vishi24 @em-abee

[zoyaashik]

Following our conversation, we've agreed to establish a new master table for fulfillment, which will include a column for fulfillment type rates. Additionally, a provider fulfillment table will be created and linked to the provider table, allowing each provider to be associated with multiple fulfillment options.

[vishi24]

@zoyaashik , please attach proof of work.