---
# System prepended metadata

title: Fusion 3PL plan of action

---

# Fusion 3PL plan of action

### Create a proof of concept that utilizes the fusion API
The first step is to figure out how pms is going to communicate with the fusion API. The first things that we need to check out are order creation, update, delete and list. We need to create a new mapping process that takes all of the internal products that are in a bill of materials for a finished good to create a list that will be used for the fusion order creation. We need to be able to update orders and delete them (for cancelled orders). The listing of orders is mainly going to be used to check the statuses of orders in order for us to mark them as fulfilled.

### Bulk import all products in fusion GUI
In order for our system to work correctly with fusion, we'll need to import all of our products in their database. (An order cannot be created for an item that is not in the system).

### Decide on a logic flow and create an implementation plan
Create a sequence diagram that covers the whole flow and have a discussion in the team around the implementation details and possible problems. 

### Write down all possible cases as user stories
In order for us to make sure that the whole process is stable, we need to figure out what are all of the possible actions/consequences that we're going to have during our transactions between pms and fusion.

### Write integration tests that verify the expected output.
It's probably best to take a test-driven approach

### Implementation
TBD...

## Questions and Answers
- Do you have typescript types for the API?
    - Doubtful. API is written in PHP.
- What is the type of service that we're supposed to use for our orders?
    - Same as shiptheory - based on package size. Talk to the team.
- What are lines?
    - Same as SKUS - lines are basically another term for SKUS.
- Can we go through the whole process of creating an item to creating an order that contains that item?
- We give our clients the ability to create custom configurations for some of the products that we sell. We don't have different SKUs for all possible configurations, because we have bills of materials where the quantities vary. In the order creation request I didn't see an input field for a let's say bill of materials ID or something like that. Does that mean that we can only create orders for items with pre-defined bills of materials assigned to their SKUS?
    - Best approach is to add each individual internal product that is in the BoM to the list of items in the order creation. This way we'll have the same approach when it comes to dynamic tampon box configurations. We'll have to add a value to each product, but since we're going to use Fusion for UK orders only, we're OK to just have the total price be split equally among all items in the order.