Purchase order can be created with following steps:
\nLoad of Article Medata using search calls. Metadata contains ArticleNames and Variations including Memory, Color and other Criteria. Can be achieved via several ways:
\nFull Search using searchV2 - takes more than a minute and is recommended to be done at night.
\nRealtime Search using searchV2 based on ArticleName and/or Manufacturer. Usually fast and takes few seconds.
\nFull Bulk Search using searchBulk - takes even more time than searchV2 but contains Calculator Data inside. Recommended to be done at night.
\nRealtime Bulk Search using searchBulk based on ArticleName and/or Manufacturer. Usually fast and takes few seconds.
\nDisplay device condition and price calculation to the Customer based on CalculatorData. CalculatorData contains questions and answers about device condition which customer should provide to get price offer for the device. Like \"screen condition: like new/used/with scratches\". Can be achieved via saveral ways:
\nUsing CalculatorData and own js-script which would use Calculator Data to calculate and display final device price based on answers.
\nIn case Article Metadata was loaded by searchV2 - calculator data needs to be taken by an additional GET call to /api/calculator/purchase/data/:articleId
\nIn case Article Metadata was loaded by searchBulk call - it already contains CalculatorData and can be used by js-script
\nUsing Realtime price calculation request to /api/calculator/purchase/calculate. This call does all calculation job and returns final price based on incoming answers.
\nUsing PrecalculatePrice option. In case there's only one Question about condition, for example \"Device Condition: Pefect/Good/Acceptable\", it is possible to add Parameter { Name: \"PrecalculatePrices\", Value: \"True\"} to searchV2 and searchBulk call to get precalculated price for each possible answer.
\nCreate Order by posting ArticleMetadata and Answers from Customer through the call /api/claim/create.
\nOptional steps available after Order creation:
\nCancel order via /api/claim/event - possible to send till Device is received by Recommerce facility. In case Recommerce receives Device of a Cancelled Order - Order becomes restored to process send back sequence.
\nUpdate Following Information via /api/claim/create:
\nContact information
\nTrack&Trace Information
\nReceive Expiration Date (date which device is expected to arrive till)
\nAsk Recommerce to send its Post Label to Customer via /api/claim/create.
\nProvide Track&Trace data via /api/claim/event to allow Recommerce to track incoming package.
\nProvide an Answer to Question from Recommerce via /api/claim/event. Most common Questions are:
\nOffer price differs from estimated price at step 2. and needs to be confirmed
\nDevice or IMEI is wrong
\nDevice is locked and needs unlocking
\nRepair order can be created with following steps:
\nLoad of Article Medata using search calls. Metadata contains ArticleNames and Variations including Memory, Color and other Criteria. Can be achieved via several ways:
\n\nCreate Order by posting ArticleMetadata from Customer through the call /api/claim/create.
\nOptional steps available after Order creation:
\nCancel order via /api/claim/event - possible to send till Device is received by Recommerce facility. In case Recommerce receives Device of a Cancelled Order - Order becomes restored to process send back sequence.
\nUpdate Following Information via /api/claim/create:
\nContact information
\nTrack&Trace Information
\nReceive Expiration Date (date which device is expected to arrive till)
\nAsk Recommerce to send its Post Label to Customer via /api/claim/create.
\nProvide Track&Trace data via /api/claim/event to allow Recommerce to track incoming package.
\nProvide an Answer to Question from Recommerce via /api/claim/event. Most common Questions are:
\nConfirm Repair Price
\nDevice or IMEI is wrong
\nDevice is locked and needs unlocking
\nAllows to get Purchase Calculator Information by:
\narticleId
\nvariationId - when ID for certain Memory/Color is known, article ID = 0 can be used with provided variationId
\nexternalArticleId - when Customer wants to use his own articleId mapped to Recommerce Variation IDs, article ID = 0 can be used when externalArticleId provided
\nIncludes article images into response. Default false.
\n","type":"text/plain"},"key":"includeImages","value":"Width of article image. Default 180px.
\n","type":"text/plain"},"key":"imageWidth","value":"Height of article image. Default 0 - means auto-scale height based on width.
\n","type":"text/plain"},"key":"imageHeight","value":"Skip returning Variations Information. Default False
\n","type":"text/plain"},"key":"skipVariations","value":"Allow to add non-Swiss layout varations to the result. Default False
\n","type":"text/plain"},"key":"includeForeignRegion","value":"Certain variationId if you know those from Search response
\n","type":"text/plain"},"key":"variationId","value":"Returns purchase prices for all possible answer combinations. Do not use if your integration supports more than one question for Article.
\n","type":"text/plain"},"key":"precalculatePrices","value":"Client Variation ID mapped to Recommerce variations
\n","type":"text/plain"},"key":"externalArticleId","value":"Optional. Allows to get prices for the future. So date in future can be gathered if partner integration supports that feature
\n","type":"text/plain"},"key":"priceByDate","value":"(Required) Article Id of device
\n","type":"text/plain"},"type":"any","value":"Creates following Order types:
\nPurchaseRequest - Recommerce buys Device
\nRepairRequest - Recommerce repairs Device
\nReplaceRequest - Recommerce sends Replacement Device to Customer
\nSwapRequest - Recommerce sends Replacement Device to Customer with Return Label to return Old Device back
\nUpdateRequest - Request to update following data on existing Order:
\nContact Data
\nTrack&Trace Data
\nReceive Expiration Date (date which device is expected to arrive till)
\nExternalRequest
\nAllows to create Order which is processed out of Recommerce
\nAllows to send Delivery Note to Customer via Email. This Delivery Not can be used to send Device to Recommerce or an External Supplier
\nErrors can be returned when manipulating with claim create or event:(Enum = IntValue)
\nINTERNAL_SERVER_ERROR = 1 - Error is internal, dev team is informed and fill fix it
\nMISSING_REQUEST = 10 - Request is not provided
\nMISSING_CONTACT = 11 - Necessary Contact Information is missing
\nMISSING_ARTICLE = 12 - Necessary Article Information is missing
\nMISSING_INPUT = 13 - Necessary Input for event is missing
\nWRONG_IMEI = 14 - Provided Imei is not valid
\nCLIENT_DATA_TOO_LONG = 15 - Client Data Length limit of 1000 is exceeded
\nAMBIGUOUS_ITEMS = 20 - System could find few Items to apply event operation to and could not identify which one is a correct one.
\nAMBIGUOUS_REQUESTS = 21 - System could find few Requests to apply event operation to and could not identify which one is a correct one.
\nITEM_NOT_FOUND = 22 - System could not find an Item to apply event operation to
\nREQUEST_NOT_FOUND = 23 - System could not find a Request to apply event operation to
\nSWAP_NOT_FINISHED = 24 - SwapBack order is not allowed till Swap is not Finished.
\nREPAIR_IS_SWAP_APPLE = 25 - Cannot create Replace order for the device cause device is marked as Swap Apple
\nCANNOT_CANCEL_REQUEST = 30 - Could not cancel request (usually cause order is already being received in the facility).
\nCANNOT_CANCEL_REFURBISH_DEVICE = 31 - Refurbish device is being already processed and cannot be cancelled.
\nCANNOT_UPDATE_REQUEST = 32 - Too late to update the Request.
\n