Reis Robotics Type PNT 350-224V/6V5 - ID3533519 kollaborativer Roboter Year of construction: 12/2009 kollaborativer roboter style:Dobot collaborative robot Cobot CR12 in den Farben Black 4262413686165

Name: Reis Robotics Type PNT 350-224V/6V5 - ID3533519 kollaborativer Roboter Year of construction: 12/2009 kollaborativer roboter style:Dobot collaborative robot Cobot CR12 in den Farben Black 4262413686165
Brand: cpacorp.vn
SKU: 34273426484
Price: 410.50 USD
Availability: InStock
Rating: 4.3303 (29 reviews)

SKU 34273426484 · ★ 4.3

EUR410.50 EUR453.50

Pay in 4 interest-free payments of $102.62 Learn more

Shipping Estimate
USA

USA

CAN

Ships within 48 hours · Estimated delivery Oct 2 - Oct 7

Gallery notes

Description

Reis Robotics Type PNT 350 224V 6V5 ID3533519 kollaborativer Roboter Year of construction: 12 2009 kollaborativer roboter style:Dobot collaborative robot Cobot CR12 in den Farben Black 4262413686165 Year of construction: 12 2009 With a 50 mm stroke and a 3 kg payload

Exchange/Return Notes

We offer a 30-day return/exchange service after receiving.
Final sale items are not eligible for returns or exchanges.
To process your return/exchange, please contact us at [email protected]
Please click here for more details>>> Return & Exchange Policy

Frequently Asked Questions for Reis Robotics Type PNT 350-224V/6V5 - ID3533519 kollaborativer Roboter Year of construction: 12/2009 kollaborativer roboter style:Dobot collaborative robot Cobot CR12 in den Farben Black 4262413686165

What should I check before buying this product for someone else?

Confirm any requirements that the recipient would need to meet. Review whether the purchase can be provided to or used by another person under the stated terms.

What should I check before ordering a product again?

Use your earlier order reference to ask the seller a precise comparison question. Check that the chosen quantity is not merely the previous order's default.

What should I clarify before asking to separate parts of an order?

Use the original order reference when explaining the request. Ask how future support requests should identify each portion.