Mapping.Works is a powerful platform that offers a wide range of capabilities and supports various input and output file formats.
🗺️ To help you understand which is best suited for your needs, please review the following mapping scenarios:
| Client opt to map: | Map to: | Via: | Input file: | Output file: |
|---|
| Their own inventory file. | Multiple supplier IDs and Gimmonix IDs. | Mapping.Works UI | Client's own Inventory File. (Required) | Cross-Mapping file between: Client IDs, Gimmonix IDs, and Supplier IDs. |
| Client opt to map: | Map to: | Via: | Input file: | Output file: |
|---|
| Their own inventory file. | Multiple supplier IDs and Gimmonix IDs. | Mapping.Works API | Client's own Inventory File. (Required) | Cross-Mapping file between: Client IDs, Gimmonix IDs, and Supplier IDs. |
| Client opt to map: | Map to: | Via: | Input file: | Output file: |
|---|
| Their own inventory file. | Multiple supplier IDs and Gimmonix IDs, along with Hotel content files. | Mapping.Works API | Client's own Inventory File. (Required) | Cross-Mapping file between: Client IDs, Gimmonix IDs, and Supplier IDs.
With Additional Content files (Images, Descriptions and Facilities). |
| Client opt to map: | Map to: | Via: | Input file: | Output file: |
|---|
| Existing suppliers in Gimmonix system and get a cross mapping file with multiple supplier IDs and Gimmonix IDs. | Multiple supplier IDs and Gimmonix IDs. | Mapping.Works UI | Not required Client's own Inventory File (can use Gimmonix ID's instead.) | Cross-Mapping file between: Client IDs, Gimmonix IDs, and Supplier IDs. |
| Client opt to map: | Map to: | Via: | Input file: | Output file: |
|---|
| Their own inventory file. | Multiple supplier IDs and Gimmonix IDs. | Map Hotels API | Hotels Information in API Request | Hotels Information in API Response : cross-Mapping between: Gimmonix IDs and Supplier IDs. |
