| A | |
| A acid | |
| A b station | |
| A battery | |
| A bond | |
| A derrick | |
| A la marengo | |
| A la maryland | |
| A level | |
| A major |
The following reference guide will allow you to create orders and retrieve their status within the FORT Warehouse Management System (WMS).
The RESTful Order API is intended to be used by an external system that would like to fulfill orders within WMS. The RESTful Order API allows a system to create and view the status of orders securely over HTTPS.
| ls | grep -e "\.json$" | while read file; do | |
| in2csv $file > "$(echo "$file" | cut -f -4 -d .).csv"; | |
| done |
| { | |
| "listings": [ | |
| { | |
| "listing": { | |
| "listingIdSHA": "1227583713283266489", | |
| "compassPropertyId": 63839393134201230, | |
| "feedListingId": "1227583713283266489", | |
| "listingType": 2, | |
| "sourceFilters": [ | |
| 3, |
| { | |
| "buildings": [], | |
| "geospatial": { | |
| "buildings": [], | |
| "centerCoords": { | |
| "lat": 37.775971, | |
| "lng": -122.412758 | |
| }, | |
| "containerSize": { | |
| "width": 703, |
| # Download in m4a format | |
| --format="ba" | |
| --extract-audio | |
| --audio-format m4a | |
| # Continue downloading if the download failed previously | |
| --continue | |
| --no-overwrites | |
| # Set track number, album name, and artist name metadata tags |
| Here’s a recap of the flow you should follow after you commit an order edit using orderEditCommit: | |
| 1. Commit the Order Edit | |
| You already do this with orderEditCommit. | |
| 2. Fetch Fulfillment Orders for the Edited Order | |
| After the edit is committed, fetch the fulfillment orders for the order to see if multiple fulfillment orders exist (which can happen if new items were added and the original fulfillment order was not eligible for modification). | |
| Operation |