Morris Costumes - Get Inventory (Primary)

This operation helps you retrieve and synchronize your primary inventory data from Morris Costumes. It uses both a static file (for product details) and two FTP files (for real-time price and quantity). Once the data is pulled, your system is updated accordingly. This ensures your catalog stays accurate and your stock levels remain up to date.

A static feed file is first retrieved from a specified source. This file rarely changes, so it is read only to extract foundational product information. Next, the system connects to an FTP location and downloads two files named “AvailableBatch_Full_Product_Data” and “AvailableBatch_Inventory_Only.” If either of these is missing, the job will fail. From these files, the integration reads current pricing and inventory quantities.

You can enable or disable the “Archive/Non-Archive Inventory” setting. If you choose to archive items that do not appear in the source feed, they are removed from active inventory. Otherwise, their quantity is set to zero. You can also decide whether this integration runs manually or on a schedule.

You begin by connecting your Morris Costumes integration and choosing or editing the FTP connection. Once connected, you configure the settings (including archive preferences and scheduling). The final step is defining and saving a mapping template that tells the system how each Morris Costumes product attribute should be mapped to your inventory fields. When everything is set, you can run the integration manually or allow it to run automatically on a set schedule.

This template defines how the “From Value” (Morris Costumes data) maps to the “To Inventory Parent Field” in your system. The interface shows a list of possible product attributes, and you can choose from several mapping modes:

In some rows, you may see “Direct Copy” chosen for fields like Parent SKU or “All Attributes.” This means those values are transferred exactly as they appear in the Morris Costumes data. The template also supports “All Images” and “All Options” to ensure every image link and product option is included. Each row can be customized so you can decide which fields to map and which to ignore or leave empty.

Once your template is saved and the integration is configured, you can run the process to fetch inventory data. If you encounter any issues, confirm that the static feed is accessible and that the FTP files “AvailableBatch_Full_Product_Data” and “AvailableBatch_Inventory_Only” are present and not empty. If the job fails due to missing or null files, check the file names and contact Morris Costumes if the files are truly unavailable.

With this setup, you can efficiently pull updated product details, pricing, and quantities into your system, keeping your inventory accurate and current.

Morris Costumes - Get Inventory (Secondary)

This operation is used to retrieve and update variant-level inventory details from Morris Costumes. Unlike the primary feed, which handles core product information, the secondary feed focuses on attributes specific to each variant. It helps ensure your system reflects accurate pricing, stock, and additional variant fields.

Similar to the primary feed, this integration downloads the latest two files from the Morris Costumes FTP:

If either file is missing, the job will fail. Once downloaded, the integration extracts price and quantity data (and any other relevant variant fields) from these files, keeping your variant-level records accurate.

You can decide whether to archive items not present in the source feed (which sets them to zero or removes them) or re-activate them if they appear again. Additionally, you can enable “Allow Create Variant” so new variant records are created if they don’t already exist in your system. This ensures your catalog dynamically expands to include new variant SKUs from Morris Costumes.

This template focuses on how the “From Value” (Morris Costumes variant data) maps to the “To Inventory Variant Field” in your system. You can choose among these mapping modes:

Below are some variant-specific attributes you might see:

These fields may be mapped or transformed based on your needs. For instance, “Cost” can be mapped directly to your variant cost field, while “SKU” could be set to match or create the variant SKU in your system. Each row in the mapping template allows you to decide how to handle that piece of data.

After configuring the integration and saving your mapping template, you can run the “Get Inventory (Secondary)” process manually or on a schedule. Make sure the FTP files are present and accessible. If they are missing or unreadable, the job will fail. Once complete, your variant-level data will be updated to reflect the latest pricing and stock from Morris Costumes.

Morris Costumes - Send Fulfillment Requests

This operation sends purchase orders (POs) or fulfillment requests directly to Morris Costumes. Once configured, orders eligible for fulfillment are turned into an XML file and placed in the /upload directory on Morris Costumes’ FTP server.

After linking your Morris Costumes FTP connection, the integration retrieves all ready-to-fulfill orders, generates one or more XML files, and uploads them to /upload. For multiple orders, the filename might be bulk_{first_poNumber}.xml; for a single order, it’s order_{poNumber}.xml.

You will need to provide:

In the “Send Purchase Orders” template, you define how each “From Value” in your system maps to “To Morris Costumes” fields. Common modes include:

Once you’ve completed the mapping and saved your settings, you can run “Send Fulfillment Requests” manually or on a schedule. The resulting XML files appear in /upload on Morris Costumes’ FTP. If errors occur:

Once the process completes without errors, your purchase orders will be available for Morris Costumes to fulfill.

Morris Costumes - Get Shipments

The Get Shipments operation retrieves detailed shipment information from Morris Costumes. This process is used to import data regarding how orders have been dispatched – including carrier details, shipping methods, tracking numbers, shipment dates, and other related information – so that your system can accurately reflect shipment statuses.

The integration connects to the Morris Costumes shipment feed via FTP. When the process runs, it downloads the shipments file, then parses and transfers the shipment details from the source (“From Value”) to the destination fields in your system (“To Shipment Field”). If the FTP file is missing or incomplete, the job will fail, ensuring that only complete shipment information is imported.

The mapping template for Get Shipments defines how each shipment-related attribute is transferred into your system. You configure each row to map a specific attribute from Morris Costumes’ shipment data to the corresponding field in your shipment record.

In addition, there is a dedicated section within the template for Shipment Item Fields, where details for each shipped product are mapped. These include item-specific attributes such as quantity, SKU, title, and any additional product-level shipment information.

Once you have defined your mapping template and saved your settings, run the Get Shipments operation. The system will process the downloaded shipment data and map it according to your configuration. If any errors occur – such as missing FTP files or incorrect mapping settings – review the configuration and ensure all required fields are properly mapped.

With this mapping template in place, your system will accurately reflect shipment details, enabling efficient tracking and order fulfillment.