Allow mapping of UPC/EAN field per new Reverb Requirement

[jpetrosky]

Reverb is now requesting valid UPC or EAN values for products marked as 'Brand New' in their system. The current (0.97) extension does not allow the mapping of a Magento product identifier field to the Reverb Universal Product Code field. UPC codes can only be updated manually or via Reverb export/import. I would assume this could be set up the same way in the extension and API calls as is currently being used for mapping of Make, Model, Description, Reverb Shipping, etc. in the Magento backend.

[kylecrum]

@jpetrosky does this not work with the field mapping page in the reverb dropdown?

[jpetrosky]

Kyle,

  No mapping available for Universal Product Code:

John Petrosky
    john.petrosky@gmail.com
On 12/13/2016 4:29 PM, Kyle Crum wrote:

  @jpetrosky does this not work with
    the field mapping page in the reverb dropdown?
  —
    You are receiving this because you were mentioned.
    Reply to this email directly, view
      it on GitHub, or mute
      the thread.

  {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/reverbdotcom/reverb-magento","title":"reverbdotcom/reverb-magento","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/reverbdotcom/reverb-magento"}},"updates":{"snippets":[{"icon":"PERSON","message":"@kylecrum in #274: @jpetrosky does this not work with the field mapping page in the reverb dropdown?"}],"action":{"name":"View Issue","url":"https://github.com/reverbdotcom/reverb-magento/issues/274#issuecomment-266867705"}}}

[kylecrum]

Reverb -> Field Mapping

You can't configure it here?

[kylecrum]

cc @dunagan5887

[dunagan5887]

@jpetrosky

The current (0.97) extension does not allow the mapping of a Magento product identifier field to the Reverb Universal Product Code field

By "Magento product identifier" do you mean the primary key on the catalog_product_entity table? A workaround for this would be to create a product attribute called magento_product_id, populate it with the catalog_product_entity table's primary key values and map that to the UPC/EAN field in the Reverb -> Field Mapping screen. Would this work for your purposes?

[kylecrum]

@jpetrosky does this work for you?

[kylecrum]

@jpetrosky actually, are you sure you want to be mapping any primary key as the UPC? If so, that sounds like quite the non-standard setup or there is a misunderstanding about what a UPC is.

[jpetrosky]

Kyle,

The issue is not our Magento attribute. The problem I believe I am having at this point is that I not certain what the Reverb API attribute (json variable) for Universal Product code is. It is not listed in the create listing API documentation (https://dev.reverb.com/docs/create-a-listing). Under the General Swagger documentation I do see the Universal Product Code defined under the Listings POST implementation ( https://reverb.com/swagger#!/listings/post_listings).

inline_model_23 { make (string, optional):

ex: Fender, Gibson , model (string, optional):

ex: Stratocaster, SG , publish (boolean, optional):

Publish your listing if draft , categories (Array[Inline Model 1], optional), sold_as_is (boolean, optional):

This item is sold As-Is and cannot be returned , photos (Array[string], optional):

An array of image URLs. Ex: ['http://my.site.com/image.jpg'] , condition (Inline Model 2, optional):

Condition , has_inventory (boolean, optional):

Set true if selling more than one , inventory (integer, optional):

Number of items available for sale. Reverb will increment and decrement automatically. , description (string, optional):

Product description. Please keep formatting to a minimum. , finish (string, optional):

Finish, e.g. 'Sunburst' , title (string, optional):

Title of your listing , year (string, optional):

Supports many formats. Ex: 1979, mid-70s, late 90s , sku (string, optional):

Unique identifier for product , upc (string, optional):

Valid UPC code , offers_enabled (boolean, optional):

Whether the listing accepts negotiated offers (default: true) , shipping_profile_id (string, optional):

id of a shop's shipping profile , shipping_profile_name (string, optional):

DEPRECATED, please use shipping_profile_id. Name of a shipping profile , location (Inline Model 3, optional), origin_country_code (string, optional):

Country of origin/manufacture, ISO code (e.g: US) , shipping (Inline Model 4, optional), seller (Inline Model 5, optional), seller_cost (string, optional):

Cost of goods in your currency (internal use only, not shown to buyers) , tax_exempt (boolean, optional):

Listing is exempt from taxes / VAT , price (Inline Model 6, optional) } Inline Model 1 { uuid (string, optional):

UUID of the category for this listing. } Inline Model 2 { uuid (string):

Condition UUID = ['fbf35668-96a0-4baa-bcde-ab18d6b1b329', '6a9dfcad-600b-46c8-9e08-ce6e5057921e', '98777886-76d0-44c8-865e-bb40e669e934', 'f7a3f48c-972a-44c6-b01a-0cd27488d3f6', 'ae4d9114-1bd7-4ec5-a4ba-6653af5ac84d', 'df268ad1-c462-4ba6-b6db-e007e23922ea', 'ac5b9c1e-dc78-466d-b0b3-7cf712967a48', '6db7df88-293b-4017-a1c1-cdb5e599fa1a', '9225283f-60c2-4413-ad18-1f5eba7a856f', '7c3f45de-2ae0-4c81-8400-fdb6b1d74890'] } Inline Model 3 { locality (string, optional):

Ex: Chicago , region (string, optional):

Ex: IL , country_code (string, optional):

Ex: US } Inline Model 4 { local (boolean, optional):

True if you offer local pickup , rates (Array[Inline Model 7], optional):

List of shipping rates. Set to null to clear rates. } Inline Model 5 { paypal_email (string, optional) } Inline Model 6 { amount (string):

The amount of money being expressed, as a decimal number , currency (string):

The currency the money will be expressed in = ['USD', 'CAD', 'EUR', 'GBP', 'AUD', 'JPY'] } Inline Model 7 { region_code (string, optional):

Country code or subregion/superregion code. Full list of codes at /api/shipping/regions , rate (Inline Model 8, optional) } Inline Model 8 { amount (string):

The amount of money being expressed, as a decimal number , currency (string):

The currency the money will be expressed in = ['USD', 'CAD', 'EUR', 'GBP', 'AUD', 'JPY'] }

I have created a field mapping from Reverb API field upc to our Magento field upc (which contains the 12 digit UPC code for the product - in this case it is 700604841442). Our Magento field is defined as a text field if that matters.

​

I then run a manual 'Bulk Sync' from Reverb > Listings, but the data still does not show on the listing in Reverb (the example below is a brand new listing that is now sitting under drafts). Our sku, name, price, mapped category, etc.. data goes to Reverb, but the UPC code does not.

​

On Thu, Dec 15, 2016 at 2:10 PM, Kyle Crum notifications@github.com wrote:

@jpetrosky https://github.com/jpetrosky actually, are you sure you want to be mapping any primary key as the UPC? If so, that sounds like quite the non-standard setup or there is a misunderstanding about what a UPC is.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/reverbdotcom/reverb-magento/issues/274#issuecomment-267413819, or mute the thread https://github.com/notifications/unsubscribe-auth/AB6auv1pWBFwQqGKcYl7SAOHfzF5Xf_Qks5rIZC-gaJpZM4LMMfb .

-- John Petrosky john.petrosky@gmail.com